Azure Traffic Manager

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or

Already have an account? Sign In »

Time
3 hours 51 minutes
Difficulty
Beginner
CEU/CPE
4
Video Transcription
00:00
>> In this video, we will see how we can use
00:00
Azure Traffic Manager to scale our application globally.
00:00
You can use a load balancer to achieve high availability
00:00
and provide resiliency for
00:00
your application in a single region.
00:00
But what if you have customers around the world?
00:00
If your application is deployed in the West US 2 region,
00:00
but your users are in Germany,
00:00
every requests they make will need to travel to
00:00
the US West Coast and back.
00:00
It doesn't matter how fast you
00:00
process the request in a datacenter,
00:00
or how fast the user center net connection is.
00:00
It takes time for the data to travel from
00:00
Berlin to Washington and back.
00:00
The time needed for the data to travel over
00:00
the network is called latency,
00:00
and it is measured in milliseconds.
00:00
Wouldn't it be faster if the requests
00:00
traveled to the Germany northeast region only,
00:00
instead of to the US west region.
00:00
In the original scenario,
00:00
the distance is approximately 5,000 miles,
00:00
while in a second, it's only a 100.
00:00
Having your application deport around the world will
00:00
significantly improve the user experience,
00:00
because it'll reduce the network latency
00:00
for the users requests.
00:00
But how do you implement that?
00:00
Well, you can use a service that provides global load
00:00
balancing functionality like Azure Traffic Manager.
00:00
Here's how it works. You deploy
00:00
exact copies of your web application
00:00
in each region you have customers.
00:00
Let's say US-West-2,
00:00
North East Germany, and Southeast Asia.
00:00
Each deployment is accessible via
00:00
deployment specific DNS name.
00:00
You configure the Azure Traffic Manager
00:00
with those three endpoints.
00:00
When a user types the URL of your website,
00:00
the request is first evaluated by the Traffic Manager.
00:00
The Traffic Manager is a global Azure service and
00:00
the user request is sent to
00:00
the end point closest to the user.
00:00
Let's say the user is in Berlin.
00:00
Azure Traffic Manager determines
00:00
the location of the user,
00:00
and instead of sending the request to West US 2,
00:00
it sends it to the closest deployment of the application.
00:00
In this case the Germany Northeast deployment.
00:00
The traffic doesn't go through the Traffic Manager.
00:00
The only thing that the Traffic Manager does is report
00:00
the user's DNS entry for my
00:00
company.com to the local application endpoint.
00:00
If another request comes from Asia,
00:00
it'll be reported to the Southeast Asia deployment.
00:00
Azure Traffic Manager also constantly
00:00
monitors the availability of the regional deployment.
00:00
If one of the region fails,
00:00
the requests will be forwarded to
00:00
the closest available region.
00:00
In essence, Azure Traffic Manager
00:00
works similar to the Azure Load Balancer,
00:00
but on a global scale.
00:00
Another way to improve the experience for your users
00:00
is to provide local caching for static content.
00:00
To do this, you can use
00:00
a content delivery network or a CDN.
00:00
A CDN is a distributed network of
00:00
servers that cache content around the world.
00:00
Those services can be hosted in the cloud provider,
00:00
but also at the local Internet provider.
00:00
This makes it even faster
00:00
for accessing the content because
00:00
the request doesn't even need to
00:00
travel to the closest Azure datacenter,
00:00
but only to the ISP datacenter.
00:00
Typical usage of CDNs are to cache HTML, JavaScript,
00:00
or CSS files, images, videos,
00:00
or other multimedia content or large downloads.
00:00
Typically those require
00:00
high bandwidth connections for faster downloads.
00:00
Caching it locally improves the user experience.
00:00
With this, we are going to wrap up
00:00
our module for Azure networking services.
Up Next