Last time I told you guys I really love the Ford story and how I see storage in the database realm. In this chapter I would like to talk about another very important piece of this realm, The Network.
If I talk to the system engineers in the environments of my clients there always seems to be some sort rivalry between storage and network on which one is to blame for troubles on the database. However, blaming one another doesn’t solve anything. We need to have the right insight into our environment to make sure we work together to solve the troubles ahead to serve the customer in his quest.
The storage part we discussed last time is responsible for storing the data, but there needs to be a medium to transport the data from the client to the server and between the server and the storage. That is where the network comes in. And to stay with my Ford story from last time, this is where other things come in to play. Speed is one of these, but speed can be measured in many ways, and that is where things seems to go south on the network part. Let’s look at a comparison to other kinds of transportation.
Consider that a city is a database where people need be “organized”. There are several ways to get the people there. Some are local, and thus the time for them to be IN the city is very short. Some are living in the suburbs, and their travel is a bit longer due to a longer road to travel and more people traveling the same transportation. If we go a bit further and concentrate on the cars again, there are a lot of cars driving to and from the city, and how fast one will come to or from the city depends on the others who have similar motivations on how quickly they want to get to their destination, how those people are performing, and what happens on the road ahead.
The network is the transportation medium for the database and needs to be treaded likewise. It is of the utmost importance that this medium is used in the correct way, and some of the data might need something like a Hyperloop to travel back and forth over medium-to-long distances, while other data could have enough with a couple of walking shoes for those shorter trips.
Having excellent visibility into the data paths and where congestion might become an issue is a very important measurement in the database world. As with traffic, it gives one insight into where troubles could arise, as well as provide the necessary information into how to solve the problem causing the jam.
For me, it is not the network that is responsible, or even storage for that matter. IT is really about the way you build and maintain your infrastructure. If you need speed, make sure you buy the fastest thing possible. However, be aware that what you buy today is old tomorrow. Monitoring and maintenance are crucial to have a database that performs well. Make sure you know what your requirements are and what you end up getting to satisfy them. Be sure to talk to the other resource providers to make sure everything works perfectly together.
Source: solarwinds GEEK SPEAK