Get an overview of the Azure Content Delivery Network service and how to configure it for a storage account.
- [Instructor] Nobody likes to wait for their files, and the content delivery network within Azure will reduce lag for your users. The content delivery network, or CDN, caches static web content in various global locations which provides the maximum throughput to users, and the benefits of this are better performance, scaling to meet workload, and the edge servers reduce traffic to the source. So how does it work? Well, it's actually quite simple, and if you've used a proxy server, this will feel very similar.
If we have our user, let's call her Jane, she requests a file using a unique domain name. DNS will then redirect the request to the best performing PoP or point of presence location. In most cases, this will be the location that is geographically closest to the user. If the edge servers at the point of presence do not have the file, then the file is requested from an Azure web app, Azure cloud service, an Azure storage account, or any other web server that is publicly available.
That file is then transferred to the edge server including the time to live. It is then transferred to Jane. When other users go to request the same file, it is transferred from the edge servers since the cache version is already available from the previous request as long as the time to live has not expired. If the time to live on that file has expired, then the whole process repeats itself. If a time to live for the file has not been specified, it will then be available on those edge servers for seven days and this is the default time to live.
Let's pop into Azure and take a look at CDN. I'm currently in my Azure account, and we're going to configure a storage account that's sitting in the Resource group, StorageOverview. I'm going to go ahead and click Add, because I need to add in the content delivery network. Start typing CDN and then choose CDN, and then Create. Next we're going to go ahead and enter a name. Again, not very descriptive on my part. My Subscription is defaulted for me.
I'm going to use the Resource group, StorageOverivew, and then I'm going to select a pricing tier. I'm just going to go ahead with an S2, and then Select it, and then Create. While this is creating, I'd like to point out that each Azure subscription is limited to eight content delivery network profiles, and each profile supports a maximum of 10 content delivery network endpoints. Our content delivery network should be available to us. I'm going to go back into our Azure Resource Manager.
I'm just going to close the blades to do so. Refresh and you'll see that our CDN demo is now available to us. Next, we're going to go ahead and add an endpoint. We're going to add a name. Again, I'm going to keep it very simple for a demo, and this does have to be unique, so I'm going to go ahead and add my initials, and apparently that's not going to work for me today. I'm going to add one more initial, and there we go. Our Origin type, where are we going to pull this data from? I'm going to pull it from Storage, and now I can go ahead and pick one of my existing storage accounts.
And let's pull it from the storageoverview.blob. If I had a specific path to pick from, I would enter it here such as, let's say, movies or JPGs. I'm going to leave the default for my header, and I can specify my Protocols, and then click Add. It will take about 60 seconds for this to be created, but it could be up to 60 minutes before it is actually available, so keep that in mind. To recap, content delivery network reduces the lag and improves the performance of your files to your end users.
- Implementing storage blobs and Azure files
- Managing access
- Configuring diagnostics, monitoring, and analytics
- Enabling and viewing logs
- Implementing Azure SQL databases
- Implementing recovery services
- Creating an Azure Backup vault
- Configuring the Azure Backup agent
- Backing up and restoring files
- Backing up an Azure virtual machine