All right in this section we're now going to have a look at CDM and also known as content delivery network
and it helps to think about how users interact with content around the web so we can understand how
the CDM fits in.
So to begin with let's think about it as if we have a source of data.
Maybe this is like a web application and people are going to Web site and retrieving a bunch of images
typically in the case of our user Theodore he would go ahead make the request to the source the origin
and the origin would serve up the content.
Now the problem here is that if people are across the globe let's say we have people in the UK Australia
South Africa et cetera.
We don't necessarily want them always coming back to the US to get their images and various pieces of
content.
So the answer to that is to use a CDM.
And what we do is we put in an edge in between the source and the user.
So Theodore for example the first time he goes to access the content we'll try to retrieve it from the
CDM.
Now the CDM doesn't have the content yet.
So the edge will go ahead to the source grab the content cache it in the edge and then serve it up to
Theodore.
Now his current experience you know if he was in say one of those regions across the globe wouldn't
be any better at this point.
However the next set of uses that go ahead and request the content they go to the edge request the content
and it's served up directly from the edge.
So there's multiple points of presence across the globe with its content it's cached and is available
to users across the globe so they get a much much better latency response time when they're serving
up the content.
Now in Asia you have three major offerings that you can utilize in order to take advantage of CDMA.
There's standard Akamai and I'll get into some of the features of these in a moment.
There's standard horizon and there's premium variety in as well and it does help to go ahead and check
out this link here because there's a huge table just of all the different features available in each
of them and we'll sort of head over there in a second and kind of cover some of them at a high level
though when you look at the offerings in the portal you'll notice a few things that really kind of stand
out as differentiating between the different services.
In particular if we look at Akamai versus horizon what you'll notice in Akamai is they put a lot of
emphasis on this media optimization.
So let's go ahead actually and switch over to the Web site and take a look at the table there and how
you can see on the web page if you scroll down to the features section you'll see this here.
It specifically mentions Dynamic Site acceleration adaptive image compression dynamic slight acceleration
object pre fetch those are features that are only available in standard Akamai and so you may be wondering
what those are.
So if we look at Dynamic Site acceleration adaptive image compression think of this like you know most
Web sites consist of an HMO page which you know you load it and then it goes out and requests all of
the images.
So what prefecture does is it actually retrieves the images of scripts embedded in the H T.M. page while
the H two miles from the browser even before the browser requests the object.
So think of it like you may go to your favorite Web page and you sort of you sign on but immediately
it's already grabbing the images while the HMO is still rendering in your page and then the other big
one here you know around adaptive image compression you know some devices if you think about it especially
mobile ones experience like slower network speeds from time to time.
I know this happens to me all the time when I'm on the train you know on the way to Chicago and you
know the network speeds kind of come and go and in these scenarios it's beneficial for the user to receive
smaller images more quickly rather than waiting for the full resolution images to come down.
This is a great feature if you go to a web page that supports this virus CDM rather than you sit in
there waiting for the images to load up it's going to serve up smaller versions of those now they may
not look you know they're not gonna be as high quality but you'll get them more frequently.
The other big one is you know around video you know the request patterns of streaming have a lot of
challenges you know when you think of a popular livestream of a new series or a new video on demand
that gets released thousands and thousands of viewers might request a stream at the same time.
And in this case you need some smart you know technology to really deal with that.
And so the technology from Akamai you know has a feature that delivers streaming media assets efficiently
to users across the globe at scale and this reduces latency is because it reduces the load on the origin
servers.
So if you think about your origin server having to kind of deal with all of this you don't have to worry
about that because that's offloaded to the Akamai engine.
That's basically taking care of that for you.
If we shift down to some of the features that are kind of unique to horizon if you scroll right down
to the bottom one in particular.
Aside from some of the management and ease of use things is this ability to use a rules engine you IRL
redirect rewrite to mobile device rules.
This is thing that's unique to the Verizon offering as well.
And this allows you to customize how each TTP requests are handled.
So for example you can block certain types of content define your own cache and policy modify H TTP
head as those are things that are unique to the variety and premium offering in particular.
So when you look at these and we'll go through in the demonstration how to kind of create a CNN point
in a moment but just as you look at these two things to stand out for the exam.
If it's optimized for media I probably should be looking at the Akamai engine and if I need something
more around rules and redirection and blocking content etc for eyes and just has a lot more features
in that area.