Welcome back. This is the start of our module, where we begin discussing the first of our exam topics. Deploy and configure infrastructure.
This first set of episodes are going to cover our first resource called storage accounts. Let's take a look at our learning objectives.
Our objectives include defining storage accounts, understanding the different types of storage accounts and looking at the characteristics of each type.
So what? It's very basic. What is a storage account
and after storage account contains data objects. You can think of it as a bucket of storage that holds blobs, files, cues, tables and virtual machine discs.
The storage account has a unique names face that could be used access over the Web using http or https
you can see on the slide some examples of these names. Spaces.
The *** trick will represent the name of the storage account, followed by the type of data and the storage account, such as a blob table, Q or file
data, and a storage account is highly available. Scaleable insecure in Azure is Global Data center. All data and a storage account is also encrypted by default.
There are several different types of storage accounts The first is a general purpose. Version one.
This is a legacy account type that is not recommended for use anymore. Except if you're using the classic azure deployment model instead of the newer armed template model,
it is recommended instead to use the newer general purpose version to storage account. This is a basic storage account for files, blobs, tables and cues.
Finally, there is blob storage, thes air blob on Lee storage accounts, meaning only blob objects can be stored them. It is recommended instead to create a general purpose V to storage account, where you can create blob storage alongside other stores, types and the same account.
We'll see the differences between these two and our demos later on.
While general Purpose V one accounts are not necessarily recommending more, we still need to know what they are. Jin won accounts, support, blobs, files, VM disc cues and tables.
Version one does not have the option of access. Tears like hot, cold or archive will cover this concept more later on.
As previously mentioned, version one is a legacy account type that may not have the latest features or best pricing
you might consider using V one if your applications are using the classic deployment model
version two of general purpose counts on Lee support the azure resource manager or armed deployment model
applications that do not require large capacity. This may mean the one is more economical,
or your application uses an older storage service. Rest a P I, and the application cannot be upgraded to use a newer one.
In most cases moving forward, you want to use version two of the general purpose storage account
speaking aversion to Let's Go over what it is about next version to also supports blobs, files, virtual machine disc cues and tables.
Version, too, will have the latest features available, as it is the newer deployment model. It will also have better pricing compared to version one. In most instances,
version to also provides access tears like hot, cold and archive.
The great thing is, if you have a current version one storage account, it could be upgraded to a version to account with no downtime and no need to copy the data to another storage account.
Now I've mentioned blobs a few times, so before we continue that the third type of storage account, let's review what Those are blob stands for binary. Large object blobs are text or binary data like lots of images, documents, videos or log files.
Thes log files are organized by containers, which are very similar to a directory in the file system.
Now there are three types of blobs. The first type is a block blob, which store text and binary data.
The second type is a pin blobs, which are optimized for upend operations like log files, where data is constantly being added to the files.
When you modifying a pin blob, the blocks are added at the end of the blob,
and our third type is Paige Blobs, which are built for storing random access files. An example of this is virtual hard drive disc being used in virtual machines. Page blobs are optimized for random read and write operations like you might find in that virtual hard disk file.
Now that we understand what blobs are, let's take a look at our third storage account type.
So blob storage accounts is our 1/3 type of storage account, and they're used strictly for on Lee storing blob storage.
Ah, blob storage account can have an unlimited number of containers and containers construe or an unlimited number of blobs
for just the blob storage account. Thes Onley support the block and a pin blobs, meaning they cannot be used to store page blobs or virtual hard disk files.
A quick note that the general purpose storage account can store all three kinds of blobs.
Blob storage also supports access tears, but at the storage account level, they only support hot or cold.
When you create a container, you can set it to an archive tear,
and we'll see this in our demo later on.
So after creating a storage account, you can build and create several different types of storage within them. And we've mentioned quite a few. These already, like blobs, files, tables and cues.
Blobs, which we've covered earlier in this episode, are large amounts of unstructured data like images, files, videos and log files.
The next kind is files which allow creating a cloud based file share. This foul share uses the server, message block or S and B standard.
These files can be mounted by multiple cloud or on premises computers, meaning you can have a cloud back file store mounted to a server in your data center
as your files can be mounted by Windows Lennox and Mac OS
tables. Store structured no sequel data. Table storage data is fast and cost effective and is typically lower and costs than a traditional sequel. Server
tables allow storing, ending number of objects in a table and a storage account can have any number of tables up to the capacity of the storage account itself.
Finally, there are accused in HK uses. A service for storing large numbers of messages. ACU can hold millions of messages up to the capacity of the storage account. These messages can be used to create a set of work items that can be worked on a synchronously, for example, a batch of images to upload.
Well, Seymour on these service is in our demos later on.
So that's it for this episode. We discuss some of the basics of storage accounts before we continue. Let's do a quick knowledge check
which storage account type supports blob storage?
If you said all three types, then you're right. The general purpose V one, V two and Blob storage all support the blob storage.
But one thing to remember is that blob storage accounts on Lee Support Block in the Pin Blob's not page blobs that are used for virtual machine hard disk
in our next episode will go Maur into detail on some of the storage account concepts mentioned in this episode, such as Performance, Tears, Access, Tears and Replication. Let's continue to the next episode.