Traffic Manager
Definition
Azure DNS-based traffic load balancer for global application availability. Like a traffic director that routes users to the best available data center.
Use Cases
- Microsoft: Global failover and performance-based routing for multi-region web applications hosted in Azure — Use Azure Traffic Manager with Performance routing to direct users to the lowest-latency regional endpoint and enable automatic failover using endpoint health probes; pair with regional services (for example, App Service or Azure Front Door/Load Balancer) to handle in-region load distribution. (Improved global availability through automatic failover and better user experience by routing users to healthier, closer regions.)
- GitHub: High availability for globally accessed developer services with regional redundancy — Use DNS-based routing with health checks and failover patterns to shift traffic away from unhealthy regions/endpoints and maintain service continuity during incidents. (Reduced downtime risk by enabling automated traffic shifting during regional or endpoint failures.)
Provider Equivalents
- AWS: Amazon Route 53
- Azure: Azure Traffic Manager
- GCP: Cloud DNS
- OCI: OCI DNS
Frequently Asked Questions
- What's the difference between Azure Traffic Manager and Azure Front Door?
- Traffic Manager is DNS-based routing: it answers DNS queries and directs clients to an endpoint (like a regional app). It does not proxy your traffic. Azure Front Door is a reverse proxy at the edge: it terminates connections, can accelerate content, provide WAF features, and routes requests at the HTTP/HTTPS layer. Use Traffic Manager when DNS-level routing is enough; use Front Door when you want edge proxying, acceleration, and layer-7 controls.
- When should I use Azure Traffic Manager?
- Use it when you need global, multi-region routing and failover across public endpoints (Azure or non-Azure) and DNS-based redirection is acceptable. Common cases include active/passive disaster recovery, active/active multi-region apps, routing users to the closest region, and shifting traffic during maintenance. If you need application-layer features (WAF, URL-based routing, caching, TLS termination), consider Azure Front Door instead.
- How much does Azure Traffic Manager cost?
- Pricing is based on factors like the number of DNS queries answered for your Traffic Manager profile and the number of monitored endpoints/health checks. Costs increase with higher query volume and more endpoints. For exact rates and regional details, use the Azure Pricing page for Traffic Manager and estimate using the Azure Pricing Calculator.
Category: networking
Difficulty: intermediate
Related Terms
See Also