one of the things that we talked about with the data security life cycle was the storage element. And when data is in storage and it could be storage and RAM, which for a short lived kind of sometimes refer to his primary storage
or storage on the hard drive on a network share somewhere, that's a more permanent location.
So when we're looking at each of the different service types, I s software service platform is a service. We want to look at the different storage types that are available to us. So we're gonna start off with, I s And you know, when we're looking at storage in an infrastructure environment,
we have two main types. We have object storage and we have block storage.
Now, ultimately, when we're talking about blocks towards very common, we're talking about a block of space typically on a drive, right? Just kind of the more you know, it's a virtual drive, but that's kind of what we're used to more from a particular format of local access in local network, restoring our dad on the drive in block format.
Now with objects storage. This is more designed for storage that we're not gonna update all the time. This is often for something we're gonna write to once or at least fewer times and read many. So if we're talking about, like, applications, applications like databases, they're always changing, right? We're not gonna use
object storage for database. That's just too much resource going back and forth
testable. A concern with object based storage
is that often when we talk about these objects,
the objects have to be synchronized, just like anything that's in multiple locations. Right? If you've got local copy if you've got a location here, location there. You know, I think about Dropbox, and I think about, you know, I've got a copy up on the server. I've got a local copy, and until those air sink,
I'm not up to date. So that is one of the concerns with object storage. Very testable.
Is that you really don't know
that your synchronized and you don't know that you have the update copy until synchronization is complete.
location, location, location.
Where's my God? That's one of the greatest security concerns. Where is our data? Is it
here in the States is it in another country? What are the laws in jurisdictions? That's just a cloud based concern. When you're looking at storing data in the cloud, where is the cloud?
Just somebody else's computer. Where is that computer will
dictate what walls and jurisdictional issues air handled. So that's certainly a security concern with I s.
Now, when we moved to data storage with past, what we really thinking about here is restoring your data in the data base, right? We're using this to create an application. This is our developer software designing, you know, some sort of af with the backend database. So how do we store information in the database?
Learned databases are either structured or their unstructured.
Most people think of a structure database, everything about sequel. We think about, you know, columns and rows and relations and all those elements. But that's not really a great structure for looking for things like video or more free flowing text or,
you know, images, the
the more multimedia based. So in those elements, we'd need an unstructured environment so past can use either of those driven by what type of data we need
and then last but not least SAS Software's a service. Well, we're entering the information
with a friend and app. That's basically, you know, gonna allow us to store information in that back in database. So we may store that information locally, we may store it on the backend database, but ultimately,
you know, when you look at this, if you look at,
uh, storage with sass, sometimes you have kind of that in application storage, where within that software element that application all element, you have the storage of the data that's produced.
Also, another term here, I would know, is a content delivery network or CD in,
and this is relevant with object storage. The I again said, maybe I should put another over with Infrastructures of service probably should do that, but ultimately with object or or in its storage.
A content delivering network is generally based on the idea that
geography can impact performance. So if I need a file and I'm located in Washington, D. C. To have to download or access that file in Hong Kong, that doesn't make sense, right way too much overhead. So ultimately, a content delivery network means that we have multiple instances off the object
distributed to various geographical locations
for the purpose of performance. That's something that'll come up