Azure Load Balancer’s international tier is a cloud-native international community load balancing resolution. With cross-region Load Balancer, prospects can distribute visitors throughout a number of Azure areas with ultra-low latency and excessive efficiency. To higher perceive the use case of Azure’s cross-region Load Balancer, let’s dive deeper right into a buyer situation. In 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–based mostly software program, targeted on serving to automobile dealerships handle all facets of their enterprise together with gross sales leads, automobiles, and buyer accounts. While it’s a international firm, most of its enterprise is finished in Europe, the United Kingdom (UK), and Asia Pacific areas. To assist its international enterprise, the shopper 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 buyer is utilizing area title service (DNS)–based mostly 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. However, if a area went down, they skilled downtime resulting from DNS caching. Although minimal, this was not a threat they may proceed to tackle as their enterprise expanded globally.
What are the issues with the present options?
Since the shopper’s resolution is international, as visitors elevated, they observed excessive latency when requesting data from their endpoints throughout areas. For instance, customers positioned in Africa observed excessive latency after they tried to request data. Often their requests had been routed to an Azure area on one other continent, which induced the excessive latency. Answering requests with low latency is a important enterprise requirement to make sure enterprise continuity. As a outcome, 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?
Given that low latency is a requirement for the shopper, a world layer 4 load balancer was an ideal resolution to the issue. The buyer deployed Azure’s cross-region Load Balancer, giving them a single distinctive globally anycast IP to load stability 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 linked from Asia Pacific areas, visitors is mechanically routed to the closest area, on this case Southeast Asia. The buyer 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. Before the replace was deployed throughout all areas, the shopper 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.
After deploying cross-region Load Balancer, visitors is now distributed with ultra-low latency throughout areas. Since the cross-region Load Balancer is a community load balancer, solely the TCP/UDP headers are rapidly inspected as a substitute of your entire packet. In addition, the cross-region Load Balancer will ship visitors to the closest collaborating Azure area to a shopper. These advantages are seen by the shopper who now sees visitors being served with decrease latency than earlier than.
Learn More
Visit 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.