In this video, Sharon provides an overview of Azure storage. She introduces the types of Azure storage accounts and explains which account type is best for the data type. This video also covers creating an Azure storage account.
- [Instructor] Let's start this course with a quick overview of Azure Storage. Using Azure Storage has several benefits including it's available from anywhere, storage scales automatically, as well as load balances automatically, it's available for both Windows and Linux clients. You can use .NET, Java, Node.js, Python, Ruby, and C++ to programmatically access as your storage and you can leverage the REST APIs for Azure Storage as well. Let's quickly take a look at Azure Storage Architecture.
We can see on our chart here, that we're broken down into two sections. Those being Iaas, infrastructure as a service and Paas, platform as a service. Disks and files fall under Iaas, so these will be your virtual machine disks and your file shares. Under platform as a service, we'll find our blobs, our tables, and our queues. There are two types of storage accounts. First, there's the general purpose storage account and this includes our tables, queues, files, blobs, and Azure virtual machine disks.
In addition to the standard storage tier, there's now a new premium storage tier as well. And there is a second storage account called blob storage and I know the naming conventions can be confusing. This is a special storage account that contains block and append blobs and has two tiers, a hot and a cool tier. We'll be talking more about these tiers in the next lesson, but for now, we're going to go ahead and continue with our overview. There are four types of services within Azure storage.
There's a blob service, this may also be referred to as the container service and this contains unstructured data. Our table service is for structured data sets. The queue service that we use for messaging and the file is used for shared storage. You may see file interchange with share. Sometimes a picture is worth a thousand words. Let's go ahead and break this down a little bit. As we can see from our storage account, we can further break that down into those four categories, the container, which contains our blobs, table, which has entities, queue holds our messages and share is for directories and files.
Let's go ahead and compare these four services and I'd like to start off with the files because that tends to be the easiest one for us to grasp. We typically use the file service for shares and tools. Think back to your on premise environment and if you have a share, maybe a Mac drive, a P drive for your users, it's the same concept. You can use the file service for migrating legacy apps, your store logs, your diagnostic data and your data dumps. We use the blob service for our backups, the blob services also used for storage of images and text, big data and our virtual machine disks sit in blob storage.
We use our queues for distributing messages and the tables can be used for device information, data for our web apps and address books. And finally, let's take a look at scale and load balancing and in order to scale and load balance storage, partitioning is used to do this. This is achieved because each object in the storage belongs to a partition and it's this partition that determines how the storage service is balanced across the servers. Again, let's look at each individual service and in this case, we'll start with blob. Each of our blobs has its own partition and it's spread across multiple servers for scaling.
When we use the table service, a partition includes all the entities with the same partition key. The queue service groups all the messages together into a single partition, which is then serviced by one server and finally, the files. All of our files in the file share are in single partition. Now that we've provided an overview of Azure Storage, let's go ahead and create an Azure Storage account. As you can I've logged into Azure, I happen to be in the design storage resource group and you'll notice that this is an empty resource group.
We don't have anything in this resource group as of yet. Let's go ahead and add in a storage account. To do so, simply click add. You can search for storage or you may actually have the icon available to you within this view as I do here. In this case, I'm just going to go ahead and click on storage account. The next blade will pop up, providing some information about the storage account. I'm going to go ahead and click create and now, we can go ahead and start configuring our storage account.
The first thing we need to do is provide a name, this will need to be a unique name because everyone is using core.windows.net. Next, you'll have to select your deployment model by default resource manager will be selected for you. Classic refers to the older portal, sometimes referred to as ASM or the Azure Service Manager. Microsoft does recommend that you do everything in the resource manager portal at this point and time. This where we pick one of the two types of storage accounts, there's a general purpose and here's our blob storage.
You'll know as soon as I click on blob storage, we do see our two access tiers. For our demonstration, I'm going to go ahead and click on general purpose. Now, please note, this is set in stone, you cannot change this after the fact. We have our two performance levels, we have standard and premium, for our demo, I'm going to leave it as standard. We do have four levels of replication, I'm going to go ahead and change this to local redundant storage for the time being. I also have the option to enable storage service encryption and enable secure transfer.
Next, you'll select your subscription if it isn't already selected. You can either create a new resource group or use an existing because I'm creating this from within the resource group. My resource group will already be populated and then your location. I'm going to go ahead and click create and also take a few moments. And we can see deployment has succeeded, I can now go ahead and start closing off some of these blades.
Once I'm back in my resource group, I'm going to go ahead and click refresh and we'll see here, that our storage account has now been created. I'm going to go ahead and click in there, what you're going to see are four types of services that are available to us. We could also go ahead and delete this account if we wanted to do so, we can move it as well, and we can open it in Explorer. We'll be exploring the options of this storage account in our upcoming lessons.
- Designing data storage
- Azure Blob storage
- Creating Blob storage using PowerShell
- Azure Cosmos DB
- Securing Azure SQL Database
- Selecting the appropriate storage option
- Virtual machine storage tiers
- Managed vs. unmanaged disks