Load balance non-HTTP(S) traffic in Azure Flashcards
Azure Load Balancer
high-performance, ultra-low-latency Layer 4 load-balancing service (inbound and outbound) for all UDP and TCP protocols.
Traffic Manager
DNS-based traffic load balancer that enables you to distribute traffic optimally to services across global Azure regions, while providing high availability and responsiveness.
Azure Application Gateway
provides application delivery controller (ADC) as a service, offering various Layer 7 load-balancing capabilities. Use it to optimize web farm productivity by offloading CPU-intensive SSL termination to the gateway.
Azure Front Door
application delivery network that provides global load balancing and site acceleration service for web applications. It offers Layer 7 capabilities for your application like SSL offload, path-based routing, fast failover, caching, etc.
Global load-balancing services
distribute traffic across regional backends, clouds, or hybrid on-premises services. These services route end-user traffic to the closest available backend.
Regional load-balancing services
distribute traffic within virtual networks across virtual machines (VMs) or zonal and zone-redundant service endpoints within a region.
HTTP(S) load-balancing services
Layer 7 load balancers that only accept HTTP(S) traffic. They’re intended for web applications or other HTTP(S) endpoints.
non-HTTP(S) load-balancing services
handle non-HTTP(S) traffic and are recommended for non-web workloads.
public load balancer
can provide outbound connections for virtual machines (VMs) inside your virtual network. These connections are accomplished by translating their private IP addresses to public IP addresses.
internal load balancer
is used where private IPs are needed at the frontend only. Internal load balancers are used to load balance traffic from internal Azure resources to other Azure resources inside a virtual network.
Zonal services
Resources can be pinned to a specific zone.
Zone-redundant services
Resources are replicated or distributed across zones automatically.
Non-regional services
Services are always available from Azure geographies and are resilient to zone-wide outages and region-wide outages.
Traffic Manager two key benefits
Distribution of traffic according to one of several traffic-routing methods
Continuous monitoring of endpoint health and automatic failover when endpoints fail
Priority
Select this routing method when you want to have a primary service endpoint for all traffic. You can provide multiple backup endpoints in case the primary or one of the backup endpoints is unavailable.
Weighted
Select this routing method when you want to distribute traffic across a set of endpoints based on their weight. Set the weight the same to distribute evenly across all endpoints.
Performance
Select the routing method when you have endpoints in different geographic locations, and you want end users to use the “closest” endpoint for the lowest network latency.
Geographic
Select this routing method to direct users to specific endpoints (Azure, External, or Nested) based on where their DNS queries originate from geographically. With this routing method, it enables you to be compliant with scenarios such as data sovereignty mandates, localization of content & user experience and measuring traffic from different regions.
MultiValue
Select this routing method for Traffic Manager profiles that can only have IPv4/IPv6 addresses as endpoints. When a query is received for this profile, all healthy endpoints are returned.
Subnet
Select this routing method to map sets of end-user IP address ranges to a specific endpoint. When a request is received, the endpoint returned will be the one mapped for that request’s source IP address.
Azure endpoints
Use this type of endpoint to load-balance traffic to a cloud service, web app, or public IP address in the same subscription within Azure.
External endpoints
Use this type of endpoint to load balance traffic for IPv4/IPv6 addresses, FQDNs, or for services hosted outside Azure. These services can either be on-premises or with a different hosting provider.
Nested endpoints
Use this type of endpoint to combine Traffic Manager profiles to create more flexible traffic-routing schemes to support the needs of larger, more complex deployments. With Nested endpoints, a child profile is added as an endpoint to a parent profile. Both the child and parent profiles can contain other endpoints of any type, including other nested profiles.
