Microsoft Azure Traffic Manager allows users to manage the user traffic distribution of various service endpoints that are located in data centers around the world. The service endpoints, which are supported by the Azure Traffic Manager, incorporate cloud services, Web Apps, and Azure VMs.
Users can use the Azure Traffic Manager, as well as the non-Azure external endpoints as well.Azure Traffic Manager utilizes the DNS (Domain Name System) in order to direct the client requests through the most suitable endpoint by applying the traffic-routing method.
If you would like to become a Microsoft Azure certified professional, then visit Mindmajix - A Global online training platform: “Azure Training” Course. This course will help you to achieve excellence in this domain.
The Traffic Manager offers several endpoint monitoring alternatives and traffic-routing methodologies to suit unique application requirements with auto-failover models. Azure Traffic Manager is robust and resilient to failures, which also includes the failures of the whole Azure region.
MS Azure Traffic Manager offers users to run websites or cloud services in data centers stationed across the globe. The Traffic Manager increases the responsiveness of applications by routing the traffic to an endpoint which has the lowest latency.
Users can perform pre-planned maintenance services on applications without having to face downtimes. Azure Traffic Manager, during the maintenance, routes the traffic to an alternate endpoint, ensuring complete service availability.
Azure Traffic Manager can support non-Azure, external endpoints, enabling its convergence with on-premises and hybrid cloud deployments. This includes, "migrate-to-cloud," "failover-to-cloud", and the "burst-to-cloud," environments.
By applying nested Traffic Manager Profiles, the traffic-routing methods can be blended together to create more flexible as well as sophisticated rules which support the requirements of the complex and the large deployments.
Azure's Traffic Manager allows users to control traffic distribution across various application endpoints. An endpoint can be referred to as an Internet-facing service, placed outside or inside the Azure.
The most significant point that needs to be understood is that Azure Traffic Manager functions at the DNS level. It uses the DNS to route clients to precise service endpoints, according to the traffic-routing rules and methods. Clients can connect directly to the chosen endpoint.
The Azure Traffic Manager, however, isn't a gateway, and neither a proxy. It cannot help the users to view the traffic between the service and the client.
Related Article: Azure DNS
Example of Azure Traffic Manager:
For instance, a company has newly launched a partner portal -
To enhance global performance, and to optimize its availability, the company uses the Azure Traffic Manager for the distribution of traffic to an available endpoint.
The application, for example, is being hosted in 3 regions of this forum. To accomplish this particular configuration, the company performs the steps listed below:
Extending the previous discussion, when the client requests for the https://partners.contoso.com/login.aspx page, They execute the below-mentioned actions to resolve DNS name in order to set up the connection.
The ATM (Azure Traffic Manager) servers get the request, and consequently, the name servers select an endpoint on the basis of
The selected endpoint is then returned as the DNS CNAME record. For this particular case, let's assume contoso-us.cloudapp.net has been returned.
This being an HTTPS endpoint, the client does the required SSL/TLS handshake, following which they make an HTTP GET request for their '/login.aspx' page. The Local DNS service caches all the DNS responses received by it. The DNS resolver located on the client's device caches the received result as well.
Caching enables DNS queries to be responded more speedily by utilizing the cache data, instead of performing queries for various name servers. The time duration of cache is typically determined by the 'time-to-live' (TTL) attribute of every DNS record. Shorter values lead to the quicker expiry of cache, and hence, more return trips to the Azure Traffic Manager name servers. Longer values essentially mean, it might need a longer time for directing the traffic elsewhere from an endpoint that has failed.
Azure Traffic Manager allows users to configure the 'time-to-live' used in Traffic Manager DNS feedbacks. It is typically 0 seconds on the lower side, and 2,147,483,647 seconds in the upper limit, compliant with the RFC-1035 maximum range.
This enables the users to determine the ideal value that is suitable to meet the requirements of their applications.
If you are interested to learn Azure and build a career in Cloud Computing? Then check out our Microsoft Azure Certification Training Course at your near Cities
Microsoft Azure Course Bangalore, Microsoft Azure Course Hyderabad, Microsoft Azure Course Pune, Microsoft Azure Course Delhi, Microsoft Azure Course Chennai, Microsoft Azure Course Newyork, Microsoft Azure Course Washington, Microsoft Azure Course Dallas, Microsoft Azure Course Maryland
These courses are incorporated with Live instructor-led training, Industry Use cases, and hands-on live projects. This training program will make you an expert in Microsoft Azure and help you to achieve your dream job.
|Microsoft Azure Infrastructure Solutions 70-533||Microsoft Azure Solutions 70-532|
|Azure Solutions Architect||Microsoft Azure Certification|
Anji Velagana is working as a Digital Marketing Analyst and Content Contributor for Mindmajix. He writes about various platforms like Servicenow, Business analysis, Performance testing, Mulesoft, Oracle Exadata, Azure, and few other courses. Contact him via email@example.com and LinkedIn.