Construct a globally resilient structure with Azure Load Balancer | Azure Weblog and Updates


Azure Load Balancer’s international tier is a cloud-native international community load balancing answer. With cross-region Load Balancer, clients can distribute visitors throughout a number of Azure areas with ultra-low latency and excessive efficiency. To raised perceive the use case of Azure’s cross-region Load Balancer, let’s dive deeper right into a buyer state of affairs. On this weblog, we’ll study a buyer, their use case, and the way Azure Load Balancer got here to the rescue.

Who can profit from Azure Load Balancer?

This instance buyer is a software program vendor within the automotive trade. Their present product choices are cloud–primarily based software program, centered on serving to automobile dealerships handle all features of their enterprise together with gross sales leads, automobiles, and buyer accounts. Whereas it’s a international firm, most of its enterprise is completed in Europe, the UK (UK), and Asia Pacific areas. To help its international enterprise, the client makes use of a variety of Azure companies together with digital machines (VMs), a wide range of platform as a service (PaaS) options, Load Balancer, and MySQL to assist meet an ever-growing demand.

What are the present international load balancing options?

The client is utilizing area title service (DNS)–primarily based visitors distribution to direct visitors to a number of Azure areas. At every Azure area, they deploy regional Azure Load Balancers to distribute visitors throughout a set of digital machines. Nonetheless, if a area went down, they skilled downtime on account of DNS caching. Though minimal, this was not a threat they may proceed to tackle as their enterprise expanded globally.

What are the issues with the present options?

Because the buyer’s answer is international, as visitors elevated, they observed excessive latency when requesting info from their endpoints throughout areas. For instance, customers positioned in Africa observed excessive latency once they tried to request info. Typically their requests had been routed to an Azure area on one other continent, which brought on the excessive latency. Answering requests with low latency is a essential enterprise requirement to make sure enterprise continuity. Because of this, they wanted an answer that withstood regional failover, whereas concurrently offering ultra-low latency with excessive efficiency.

How did Azure’s cross-region Load Balancer assist?

Provided that low latency is a requirement for the client, a worldwide layer 4 load balancer was an ideal answer to the issue. The client deployed Azure’s cross-region Load Balancer, giving them a single distinctive globally anycast IP to load steadiness throughout their regional places of work. With Azure’s cross-region Load Balancer, visitors is distributed to the closest area, guaranteeing low latency when utilizing the service. For instance, if a buyer related from Asia Pacific areas, visitors is robotically routed to the closest area, on this case Southeast Asia. The client was in a position so as to add all their regional load balancers to the backend of the cross-region Load Balancer and thus improved latency with none extra downtime. Earlier than the replace was deployed throughout all areas, the client verified that their metrics for knowledge path availability and well being probe standing are one hundred pc on each its cross-region Load Balancer and every regional Load Balancer.


The figure shows three panels each of an Azure region: East Asia, UK West, and South Africa North, that each contain a virtual network. Within each virtual network, there are 2 virtual machines that are meant to represent the backend resources. In addition, each panel shows a regional Azure Load Balancer that points to each backend resource. This symbolizes that the load balancer distributes traffic to each of the backend resources. Furthermore, above all 3 panels is an Azure cross region Load Balancer, that points to each individual regional load balancer. The Auto DMS’s end user, shown by a user icon, will interact with the cross region load balancer to request information from the backend.

After deploying cross-region Load Balancer, visitors is now distributed with ultra-low latency throughout areas. Because the cross-region Load Balancer is a community load balancer, solely the TCP/UDP headers are shortly inspected as an alternative of your complete packet. As well as, the cross-region Load Balancer will ship visitors to the closest collaborating Azure area to a shopper. These advantages are seen by the client who now sees visitors being served with decrease latency than earlier than.

Be taught Extra

Go to the Cross-region load balancer overview to study extra about Azure’s cross-region Load Balancer and the way it can match into your structure.


Leave a Reply