In this video, we will see how we can use azure traffic manager to scale our application globally.
You can use a load balancer to achieve high availability and provide resiliency for your application in a single region.
But what if you have customers around the world
if your application is deployed in the West US two region, but your users are in Germany,
every request they make will need to travel to the U. S. West Coast and back.
It doesn't matter how fast you process the request in the data center or how fast the user center net connection is.
It takes time for the data to travel from Berlin to Washington and back
the time needed for the data to travel over the network is called latency, and it is measured in milliseconds.
Wouldn't it be faster if the request traveled to the Germany Northeast region only instead of to the US West region?
In the original scenario, the distance is approximately 5000 miles, while in the second
Having your application deport around the world was significantly improve the user experience because it will reduce the network latency for the user's requests But
how do you implement that?
Well, you can use a service that provides global load balancing functionality like azure traffic manager.
Here's how it works.
You deploy exact copies of your Web application in each region. You have customers,
Let's say US West two, North East Germany and South East Asia.
Each deployment is accessible via deployment specific. DNS name.
You can figure the azure traffic manager with those three end points.
When a user types that you are all of your website. The request is first evaluated by the traffic manager.
The traffic manager is a global azure service, and the user request is sent to the end point closest to the user.
Let's say the user is in Berlin.
Azure traffic manager determines the location of the user,
and instead of sending the request to West US two, it sends it to the closest deployment of the application.
In this case, the Germany Northeast deployment.
The traffic doesn't go through the traffic manager.
The only thing that the traffic manager does is report the user's DNS entry for my company dot com to the local application endpoint.
If another request comes from Asia, it'll be reported to the Southeast Asia deployment.
Azure traffic manager also constantly monitors the availability of the regional deployment.
If one of the region fails, the requests will be forwarded to the closest available region.
In essence, Azure traffic manager works similar to the azure load balancer. But on a global scale,
another way to improve the experience for your users is to provide local cashing for static content.
To do this, you can use a content delivery network, or CDN.
A cdn is a distributive network of servers that cache content around the world.
Those services can be hosted in the cloud provider, but also at the local Internet provider.
This makes it even faster for accessing the content, because the request doesn't even need to travel to the closest Azure data center, but only to the ISP data center.
Typically, those require high bandwidth connections for faster downloads.
Cashing it locally improves the user experience.
we are going to wrap up our modules for azure networking services