Load balancing aims to optimize resource use, maximize throughput, minimize response time, and avoid overloading any single resource. It can also improve availability by sharing a workload across redundant computing resources.
Azure provides various load balancing services that you can use to distribute your workloads across multiple computing resources - Application Gateway, Load Balancer, Traffic Manager and Front Door.
- Application Gateway:
- Azure Application Gateway is a web traffic load balancer that enables you to manage traffic to your web applications
- Application Gateway can make routing decisions based on additional attributes of an HTTP request, for example, URI path or host headers.
- We can use Application Gateway with Web Application Firewall (WAF) for a scalable and secure way to manage traffic to your web applications.
- Load Balancer
- Azure Load Balancer operates at layer 4 of the Open Systems Interconnection (OSI) model.
- It's the single point of contact for clients. Load balancer distributes inbound flows that arrive at the load balancer's front end to backend pool instances.
- The backend pool instances can be Azure Virtual Machines or instances in a virtual machine scale set.
- A public load balancer can provide outbound connections for virtual machines (VMs) inside your virtual network
- Public Load Balancers are used to load balance internet traffic to your VMs
- An internal (or private) load balancer is used where private IPs are needed at the frontend only.
- Internal load balancers are used to load balance traffic inside a virtual network.
- Traffic Manager
- Azure Traffic Manager is a DNS-based traffic load balancer. This service allows you to distribute traffic to your public-facing applications across the global Azure regions. Traffic Manager also provides your public endpoints with high availability and quick responsiveness
- Front Door
- Azure Front Door is a global, scalable entry-point that uses the Microsoft global edge network to create fast, secure, and widely scalable web applications.
- With Front Door, you can transform your global consumer and enterprise applications into robust, high-performing personalized modern applications with content that reach a global audience through Azure
- Front Door works at Layer 7 (HTTP/HTTPS layer)
Below information will help you to choose service wisely:
- If you want to load balance between your servers in a region at the application layer, review Application Gateway.
- To do network layer load balancing, review Load Balancer.
- If you are looking to do DNS-based global routing and do not have requirements for Transport Layer Security (TLS) protocol termination ("SSL offload"), per-HTTP/HTTPS request or application-layer processing, review Traffic Manager.
- If you need to optimize the global routing of your web traffic and optimize top-tier end-user performance and reliability through quick global failover, see Front Door.
I hope this article will help you to understand the available 'Azure Load Balancing Service'.
Thanks for reading this article. Please share your comments and review for the same.