Comparison of Azure Front Door, Traffic Manager, Application Gateway & Load Balancer
With the introduction of Azure Front Door, the official documentation has new guidance [compare with old] on load balancing options and a decision tree -
Related: Compared: Azure Load Balancer, Application Gateway, Traffic Manager
Options | Azure Front Door | Traffic Manager | Application Gateway | Azure Load Balancer |
Description | Offers Layer 7 capabilities for your application like SSL offload, path-based routing, fast failover, caching, etc. to improve performance and high-availability of your applications. | DNS-based load-balancing service that operates only at the domain level. For that reason, it can't fail over as quickly as Front Door, because of common challenges around DNS caching and systems not honoring DNS TTLs. | Provides application delivery controller (ADC) as a service, offering various Layer 7 load-balancing capabilities. | Zone-redundant, high-performance, low-latency Layer 4 load-balancing service (inbound and outbound) for all UDP and TCP protocols. |
Global/regional | Global | Global | Regional | Regional |
Recommended traffic |
HTTP(S) | non-HTTP(S) | HTTP(S) | non-HTTP(S) |
SLA | 99.99% | 99.99% | 99.95% | 99.99% |
You only need routing (performance- or geography-based) and high availability | Suitable | |||
You need SSL termination (also called SSL offloading) | Suitable | Suitable | ||
You need application layer features like URL rewriting and WAF |
Suitable | Suitable |
Related: Compared: Azure Load Balancer, Application Gateway, Traffic Manager
Comments
Post a Comment