Hello and welcome back to Siberia is Microsoft Azure Administrator, A Z 103 course. I'm Will Carlson. And this is Episode 25 Azure CD and or content delivery network.
In today's episode, we're gonna explain a little bit about what a content delivery network is, and then we're gonna walk through the process of configuring one here in Azure.
follow me here in this image and let's think about an origin server being a storage account that has any number of files that I want to ultimately share. And this origin server is in the United States
now when a typical user request those files, if they are in the same region in the United States as the server, that request is going to be relatively timely.
But let's imagine for a second that this server is in the United States and Alice over here is in Australia, and those files are going to have to trippers all of the wires between the United States and Australia. That's gonna increase Leighton see and make it take longer and be less responsive for Alice to get those files. So what can we do?
we could spend up a copy of those files over in Australia and store them in two places.
But now all of a sudden we have data consistency issues, and we're paying for twice the storage of those files.
And then what happens when we have a series of users that want to access those files in the UK?
Do we copy our data over there and spend up another server? And now all of a sudden we're paying for three times the storage? Well,
that's not the best answer, and that's part of the problem that a cdn is set up to help us solve.
So what is a CD ender
if you're not familiar with a CD en Aura content delivery network? The point is for the origin server to replicate data to a point of presence or an edge server when the user requests it and these edge servers are going to be closer to the users. So when our example here are origin, Server is in the United States.
Alice is in Australia.
She requests, via a custom your ill of the CD in she requests our files and the CD in EJ servers realize they don't have those files, they will reach out to the origin and pull those files in.
And as long as the T. T. L, or the time to live is long enough, when the next user requests access to those files from Australia, there cashed on the edge servers and the user gets them from the edge servers.
The same thing would apply over here in the UK As soon as a user from the UK requested those files, they would be pulled into the point of presence edge servers. And then from that point forward, when any users requested those files in the UK, they would get them from the edge servers that are closer to them.
That also does something interesting on the processing time required of this particular server.
It goes down because the edge servers are the ones doing the processing, in this case for a storage account, the edge servers of the one storing that information and you don't pay for that storage you paper, the terabyte of the data transferred out of those edge servers.
So now that you think that's great, because you have a worldwide room of users that want to access your files in your storage account and you want them to be able to do that efficiently. But how do you go about setting up a CD in here and portal?
Well, let's get right to it.
We're gonna go straight into portal. We're gonna go to create a resource, and we're gonna look for CD in.
We're gonna click on that and hit create
we're setting up now is going to be the CD in profile, and we can name that whatever we want.
We're going to tie that to a subscription, and we're gonna assign that to the resource group that we want the CD in profile to live in.
Now we have a few options here in Azure of the pricing tier, and it's gonna depend on what provider ultimately you use to get this done
to learn more about the difference between these options and they're full pricing details simply click here, but for now we're gonna go ahead and so, like standard Microsoft pricing,
and that sets up the CD in profile. We could go ahead and select create here, and that would create this CD in profile for us. And then we could go in an associate different CD and in points. Four different service's be that Storage Cloud Service's Web, APS, whatever it was that we chose at a future day.
But we're gonna go ahead now, though, and create this CD in in point while we're here.
Now. One interesting thing here is that this has to be unique again. This is going to create the domain that users will use to get to my CD in. So it has to be don't unique within the azure environment. So
no other dot azure ej dot net accounts can use this same mural or the same string for their seeding it.
We also have a couple of options of origin types that I mentioned just a second ago for a Z 103 You really only need to be familiar with the storage Cdn,
and then we're gonna go in here and select the origin host name. Now, we could select this really nasty one, which is the idea of that account, or we can select a little bit prettier one, or if we had set a custom domain, we could go ahead and select that one as well. But I'm gonna go ahead and select this.
I'm gonna go ahead and hit, create,
and that's created our CD End in Point and our CD in profile.
Now there's a few other things that we need to discuss in relation to CD ends. So we're gonna go back up here instead of create resource we're gonna get all service is
we're gonna search for CD, and then we're gonna flick here into CD and profiles,
and you can see the CD in profile that we created previously. Let's open that up and have a poke around.
Now that we're here in the CD and or the CD in profile, I can see all of the end points that are associated with that profile.
If I go ahead and click on down into the storage in point that we just created, I can see a number of additional functions. First of all, if we want to get to our storage CD and end point, you can see the u. R l hear that One thing to keep in mind is that it could take a little bit of time for this in points to populate and propagate through the entire azure network.
Back in the end point itself. I can come here to origin
and see a little bit more about the CD, an end point. And what protocols are gonna be allowed to navigate that in point? So I could simply uncheck http. It's saved, and then I forced secure transfer to that storage in point. I could also come here into custom domains and set up a custom domain, which again would change the or L and make it a little more user friendly.
Compression here is going to be a way that you can optimize the storage
in your CD in because again, the pricing for these storage CD ends or CD ends in general is going to be on the outbound terabytes. So anything you can do to compress the file's coming out of your CD in is just gonna lower that cost.
CD ends also support the concept of geo filtering. So if I only if I wanted to prohibit certain countries from accessing my setia,
I could select, block and select the country codes I wanted to block,
or if I only wanted to allow them from certain countries, I could select, allow and then check mark only the allowed country's gonna discard these changes for now. So we talked about a number of things in today's episode, but I do want to call out here one additional point about timeto live. And here in Azure, depending on the pricing tier that you choose,
will depend on how gran you Aly you can control the timeto live.
And essentially all that time to live does is it tells the endpoint servers how long to keep your information cashed before it expires or is renewed?
We talked about some of the reasons to deploy a CD in so offloading some of the storage and or compute requirements for our origin computers and for increasing performance for our users all around the globe.
We went through the steps of creating the End point and the CD in profile to deploy a CD in and Azure, and we walked through the fact that there are various different pricing options. I would step through those pricing options and at least be familiar with some of the functionality differences between them. For a Z, one of three
coming up, we're gonna talk about some ways to backup files in folders in azure, using some built in tools to ensure that you don't lose any information and have quality backups
on a regular basis. Thanks for joining me today, and I'm looking forward to the next episode.