Why Nested Azure Traffic Manager profile required?

Hello, All Techy, here in this blog I will describe Why do we require Nested Traffic Manager Profile in Azure? before proceeding, I am assuming you already have good understanding of all basic concepts of Azure Traffic manager, Routing method etc.

Last week while designing one critical architecture, I trapped in one critical scenario. I kept in mind to share this challenging experience with you. As you all know Azure Traffic Manager have different Traffic-Routing methods.  This routing methods decides the way how to route the incoming traffic to various available endpoints.  Below is the list of Traffic-routing methods.

  • Priority
  • Weighted
  • Performance
  • Geographic
  • Multivalue
  • Subnet

You can get details more details about it on Microsoft web site like how each traffic-routing method works. Let’s start on exact scenarios.

Scenario / Requirement   

Customers requirement is :

  • Application should be deployed in 4 different regions.
  • End users should use the closest endpoint for lowest network latency
  • Each region should have 1 backup instance. if one goes down (because of some issue or maintenance purpose) another should be available.

This are some of the important point of actual requirements.  

Technical Issue  

Above requirement points are very clear and clean. Deploy Application in 4 different regions. (West Europe, West Asia, West US, East Asia). To implement 2nd point you will require to use “Performance” Traffic-routing method. This method will automatically connect to geographically closest point for lowest network latency. Till this part its perfectly fine but 3rd point is important.

You already added traffic manager “Performance” routing method to manage traffic in between these 4 regions. Next requirement is each region should have 2 instances for backup purpose if one instance goes down backup instance will be available. For this we will require Traffic managers “Priority” Traffic-routing method. One traffic manager profile supports only single traffic-routing method.

One traffic manager profile supports only single traffic-routing method.

Solution

As we can’t set 2 traffic-routing methods in one single traffic manager profile, however we can design architecture where we can add 2 different Traffic manager profile. As below.

As Nested Traffic profile you can add multiple traffic manager profile. There can be different combinations of Traffic-routing methods. You must choose correct routing method as per requirements. You can nest Traffic Manager profiles to combine the benefits of more than one traffic-routing method. Nested profiles allow you to override the default Traffic Manager behavior to support larger and more complex application deployments. The above examples illustrate how to use nested Traffic Manager profiles in various scenarios.