Learn how to define your own storage requirements, including capacity and growth.
- [Instructor] So, let's talk about understanding storage requirements. First thing you need to understand is that it's all about the growth. Basically, as you grow your business, you're going to spin-off more data but also other things such as binary stuff such as images and multimedia files and videos and things like that depending on how your business is going to be structured. So, assume exponential growth. Assume that the curve is going to be very steep and up to the right as you select your storage providers and understand the capabilities of them, whether it's hardware, whether it's cloud-based.
Data is the big one. So, data growth, in terms of the amount of data that we're going to store and maintain, is going to typically explode if you're a typical Global 2000 company. The reason is we're using data for analysis, we're centralizing data, we have many versions of the same data, we have data warehouses, data marts, we use the big data systems, things like that. So, the more systems that are spinning off information and we have both devices and people and things that are spinning off scads of information, then the more storage you're going to need.
Files, so we have to maintain file systems and files that exist on file systems. They could be binary files as big as a terabyte or they could be very small text files. They have to be maintained, stored, organized, backed up, managed. Multimedia data, video, voice, images, all those things take up huge amounts of storage. We all know that when we run out of storage on our laptops or on our phones that deleting videos and pictures are the easiest way to get the storage back and other stuff.
So, we have structured and unstructured data that we're dealing with and we're talking about structured data sometimes. And so, structured data could be any number of different types of information, could be PDF files, it could be PowerPoint presentations, it could be other things that really haven't been considered data in the past. But they're things that needed to be stored and managed and called through as we understand our business better by understanding the data that's innate or native to the business. Text, we have lots of text, lots of documents, lots of information that has to be managed.
Not only is it a good idea to manage it on behalf of the business and and end users but in many instances, they are legal requirements. We have to have system that are maintained, data that's maintained for a long period of time based on legal issues and Sarbanes-Oxley, and other requirements and other areas of compliance including HIPAA in the health care industry, things in the financial industry as well. So, the first thing is focus on capacity. So, what does the capacity need to be over time? The nice thing about cloud computing is you really don't have to guess at a number.
In other words, we don't have to come up with something we think it's going to be in two years, four years, six years. We can leverage cloud-based systems and they're only going to charge us for what we're leveraging or capacity we're using. However, it's still a bill that has to be paid and therefore, it's still important that we understand how much money it's going to cost over a long period of time. Focus on the need, so, understand how people are going to consume storage volume. So, application developers are going to consume storage very differently than the accounting group very differently and then the manufacturing group and having a good understanding in terms of what consumption patterns of storage are going to be for the particular areas in the business is absolutely imperative.
We saw in the previous example when we allocated storage, we had different sorts of platforms and different sorts of volumes that we needed amounts and you're going to find that the systems are going to be completely different from one organization to the next and that even though you're running on a cloud provider such as Amazon Web Services, very little to accommodate the differences by basically serving up different platforms and different types of storage to meet your needs. Focus on usage patterns. So, how are people leveraging this storage in ways that are going to be basically generalized patterns that we can put in categories.
So, we talked earlier about developers using one way, HR uses it another way, inventory uses it at a different way, things like that, or what are the patterns of use? In other words, what times of day are they leveraging the storage systems. What kind of back-up do they need? What kind of other infrastructure do they need in place to support their storage? And you do that by not necessarily trying to resolve the requirements of every individual who's leveraging your storage system, but the patterns of use that are basically emerging from all the individuals and all the applications and all the other resources that are leveraging storage.
So, this is an example of Microsoft as your operational insights and this allows you to basically monitor a storage systems but as a cool feature, it allows you to project storage as well. So, we can look at what we're using now and the patterns of use, and therefore, project into the future what that use looks like in terms of capacity storage that you need. So, as we're looking to improve and enhance our storage systems that exist in the cloud, this sort of tool and there's other tools like it for AWS and Google allow you to, in essence, look at where we're taking storage based on use of compute cycles, use of a memory, other base systems, number of users, number of applications, and what that looks like, and just basically make some good predictions in terms of what storage capacity is required going forward into the future.
So, a couple of things to remember, it's about the math. So, when we talk about storage, it's very much like when we talk about real estate, location, location, location. When we talk about storage, it's capacity, capacity, capacity. So, what can we do to figure out what the capacity is going to be based on the current patterns of consumption, based on the projected growth of the business, based on where things are going from a technological point of view. The chances are, it's going to be growing, not contracting, but the rate of growth or the capacity that you're going to need should be determined by mathematics and by you understanding that it's about understanding the patterns of growth and growing those patterns into the future.
Leverage your tools like the one we just saw but you don't have to necessarily rely on those tools. Those tools are basically aiding you and helping you move forward.
- Block storage, object storage, and file storage
- Planning cloud storage
- Allocating storage instances on AWS
- Securing storage instances
- Understanding usage-based accounting
- Defining costs, projected growth, and implementation plans
- Reviewing cloud storage use cases