Traffic Manager
Traffic Manager is a DNS based traffic load balancing service
Overview
- Traffic manager is a global service. You do not select a region when you deploy it.
- Traffic Manager uses DNS to direct client requests to the most appropriate service endpoint based on a traffic-routing method and the health of the endpoints.
- Traffic Manager can improve the availability and responsiveness of your application.
- Traffic Manager can be used to:
- Load balance incoming traffic across multiple Azure regions
- Route traffic to a specific region based on the client’s geographic location
- Route traffic to a specific region based on the endpoint’s health
- Route traffic to a specific region based on the endpoint’s performance
- Traffic Manager supports multiple DNS routing methods, including:
- Priority
- Weighted
- Performance
- Geographic
- Multi-value
- Traffic Manager can be used with Azure services, external services, and on-premises services. The endpoint must be public.
- Traffic Manager does not support routing to private IP addresses.
Endpoint types:
- Azure Endpoint:
- Cloud Service, Web App, Public IP
- External Endpoint
- Nested TM Profile
Traffic Routing Methods
- Priority Routing Method
- Traffic Manager directs traffic to the primary endpoint. If the primary endpoint is unavailable, Traffic Manager fails over to the secondary endpoint.
- Performance Routing Method
- Traffic Manager directs traffic to the endpoint with the lowest latency.
- Geographic Routing Method
- Traffic Manager directs traffic to the endpoint based on the geographic location of the client (where the DNS query originates from).
- Subnet Routing Method
- Traffic Manager directs traffic to the endpoint based on the IP address of the client.
- Weighted Routing Method
- Traffic Manager distributes traffic across multiple endpoints based on a user-defined weight.
- Multi-value Routing Method
- Traffic Manager returns multiple endpoints in the DNS response, and the client selects one.