1) Priority traffic-routing method
The Traffic Manager profile contains a prioritized list of service endpoints. By default, Traffic Manager sends all traffic to the first (highest-priority) endpoint. If the first endpoint isn't available, Traffic Manager routes the traffic to the second endpoint. If both the first and secondary endpoints aren't available, the traffic goes to the third, and so on.
2) Weighted traffic-routing method
This method is deployed if you want to distribute traffic across a group of endpoints, either evenly or consistent with weights (ratio), which you define.
3) Performance traffic-routing method
Deploying endpoints in two or more locations across the world can improve the responsiveness of the many applications by routing traffic to the situation that's closest.
The 'closest' endpoint isn't necessarily closest as measured by geographic distance. Instead, the 'Performance' traffic-routing method determines the closest endpoint by measuring network latency.
Traffic Manager maintains an online Latency Table to trace the round-trip time between IP address ranges and every Azure datacenter.
4) Geographic traffic-routing method
Traffic Manager profiles are often configured to use the Geographic routing method in order that users are directed to specific endpoints (Azure, External or Nested) supported which geographic location their DNS query originates from.
When a neighborhood or a group of regions is assigned to an endpoint, any requests from those regions gets routed only this endpoint.
Traffic Manager uses the source IP address of the DNS query to figure out the region from which a user is querying from – usually this is often the IP address of the local DNS resolver doing the query on behalf of the user.
Consider a Geographic Routing type profile with two endpoints - Endpoint1 and Endpoint2. Endpoint1 is configured to receive traffic from Ireland and Endpoint2 is configured to receive traffic from Europe. If the dns query originates from Ireland, it's always routed to Endpoint1.
If an endpoint match is found which endpoint is within the Stopped state, Traffic Manager returns a "NO DATA" response.
It is strongly recommended that customers using the geographic routing method associate it with the Nested type endpoints that has child profiles containing a minimum of two endpoints within each.
Nested Traffic Manager profiles
In this configuration, traffic directed via the parent profile distributes traffic across regions normally.
Within West Europe, the nested profile distributes traffic to the assembly and test endpoints consistent with the weights assigned.
5) Multi value traffic-routing method
The Multi value traffic-routing method allows you to urge multiple healthy endpoints during a single DNS query response.
This pattern can increase the supply of a service and reduce the latency related to a replacement DNS query to get a healthy endpoint. Multivalve routing method works as long as all the endpoints of type ‘External’ and are specified as IPv4 or IPv6 addresses.
6) Subnet traffic-routing method
The Subnet traffic-routing method allows you to map a group of user IP address ranges to specific endpoints during a profile.
The IP address to be mapped to an endpoint are often specified as CIDR ranges (e.g. 1.2.3.0/24) or as an address range (e.g. 1.2.3.4-5.6.7.8).
Comments