Azure Load Balancer Vs Traffic Manager

So you want to know the key differences eh!

Lets take a dive….

So basically the two technologies help distribute traffic in Azure.  We’ll start by looking at the Azure Load Balancer.

 

Azure Load Balancer

This method is native to Azure and routes traffic between one or more private endpoints that sit behind a internal or external (public) endpoint:

  • Performs on the Network Level (Layer 4)
  • Supports any application protocol
  • Endpoints: Azure VM and Cloud Service role instances (in the same region)
  • Used for internal and internet facing applications
  • Monitoring: Using ‘Probes’ (every 15 second health check)
  • Round Robin Only

 

Traffic Manager

This is a more advanced method of routing traffic has it serves as an intelligent DNS Resolver.  Works well in a hybrid setup where services are split between onprem and Azure.

  • Performs at the DNS Level
  • HTTP/S endpoint is needed for endpoint monitoring
  • Same as Azure Load Balancer but includes Azure Web Apps & External endpoints
  • Supports only Internet facing applications
  • Supported by HTTP/S Probes

Traffic Manager uses three load-balancing methods to distribute traffic:

  • Failover: Use this method when you want to use a primary endpoint for all traffic, but provide backups in case the primary becomes unavailable.
  • Performance: Use this method when you have endpoints in different geographic locations and you want requesting clients to use the “closest” endpoint in terms of the lowest latency.
  • Round Robin: Use this method when you want to distribute load across a set of cloud services in the same datacenter or across cloud services or websites in different datacenters.