Tuesday, April 16, 2024
HomeCloud ComputingWorld distribution options with Microsoft Azure

World distribution options with Microsoft Azure

This put up was co-authored by Dave Burkhardt and Sami Modak.

As a part of your cloud journey, essential purposes must be deployed in a number of Azure areas to make sure excessive availability to your world buyer base. When reviewing Azure’s varied world visitors distribution options, ask your self, “Which possibility is the very best one for my utility?”

On this weblog, you’ll find out about every world visitors distribution answer Azure provides, and which answer is the very best one to your internet-facing cloud structure. Presently, Azure provides completely different choices for distributing world visitors. Microsoft Azure Entrance Door is a content material supply community (CDN) service with utility layer load balancing capabilities. Azure cross-region Load Balancer is a world community layer load balancer. Lastly, Azure Site visitors Supervisor is a website identify service (DNS)-based visitors distribution answer. 

Choosing the proper world visitors distribution answer

You’ll find out about three instance corporations—Contoso1, Contoso2, and Contoso3. For every firm, we are going to dive into their utility’s state of affairs and determine which world visitors distribution answer is the very best one for them.

Buyer state of affairs 1—wholesale distributor

Contoso1 is a big wholesale distributor that has areas all around the globe. Contoso1 has been going by way of a big technological transformation and has been migrating companies to Azure. One of many purposes being moved to Azure is their backend stock administration software program. This utility is answerable for offering customers with details about stock standing and updating stock information after a transaction has occurred. As a part of their migration the workforce at Contoso1 has strict necessities that must be met by a world distribution answer.

  • First, all visitors sort will likely be layer 4 and have to be served with ultra-low latency. As well as, the applying requires a regional redundancy with automated visitors fail-over within the occasion a area is down, to make sure excessive availability.
  • Second, the applying requires a static IP deal with that the applying’s frontend will persistently ping.
  • Lastly, any updates made to regional deployments shouldn’t have an effect on the general backend stock utility.

Given all the necessities laid out by Contoso1’s, Azure cross-region Load Balancer is an ideal answer for his or her utility. Azure cross-region Load Balancer is extremely optimized at serving layer-4 visitors with ultra-low latency. Moreover, cross-region load balancer gives geo-proximity routing, which implies all Contoso1’s shops visitors will likely be forwarded to the closest regional deployment to them. Azure cross-region Load Balancer additionally gives automated failover. Within the occasion one among Contoso1’s regional deployment is unhealthy, all visitors will likely be serviced by the subsequent wholesome regional deployment. As well as, cross-region load balancers present customers with a static globally anycast IP deal with, through which Contoso1 doesn’t have to fret about their IP deal with altering. Lastly, Azure cross-region Load Balancer will enable Contoso1 to replace its regional deployments behind a single world endpoint with none influence on its finish customers.

The following image shows Azure cross-region Load Balancer connected to three regional load balancers. The regional load balancers are spread across the globe, which showcases how cross-region load balancer can achieve global load balancing.

Buyer state of affairs 2—social media firm

Contoso2 is a world social media platform. As a social media web site, they should serve each interactive and static content material to their customers across the globe as shortly and reliably as doable. Most lately, as a consequence of Contoso2’s distinguished standing as a social media platform, they’ve skilled an outage with their on-premises hosted web site due to a DDoS assault. That stated, Contoso2 has the next strict necessities as they migrate to Azure:

  • A platform that may ship each static and dynamic content material to their shoppers across the globe with the utmost efficiency and reliability.
  • Capacity to route content material to each their cell and desktop customers as shortly as doable.
  • Simply combine with Azure’s DNS, Net Software, Storage, and Software Gateway merchandise.
  • DDoS safety.
  • Cut back safe sockets layer (SSL) load on Contoso2’s utility servers, and as a substitute course of SSL requests on the sting for quicker person expertise for Contoso2’s world purchasers.

Azure Entrance Door is a perfect answer to allow accelerated and extremely resilient net utility efficiency for optimum supply of static and dynamic content material across the globe:

  • Static Content material—Contoso2’s cached static content material might be served from Azure Entrance Door’s 185 world edge factors of presence (PoP) areas. To make sure the utmost efficiency and resiliency, Azure Entrance Door makes use of the Anycast protocol to ensure the Contoso2’s shopper’s requests are served from the closest world edge areas.
  • Dynamic Content material—Azure Entrance Door has an arsenal of visitors acceleration options. Consumer to Azure Entrance Door PoP visitors is once more optimized by way of the Anycast protocol. Though because it particularly pertains to dynamic workloads, edge PoP to buyer’s origin connections are optimized by way of break up TCP. This system allows the visitors to terminate the TCP connection to the closest edge PoP and makes use of lengthy dwelling connections over Microsoft’s world non-public large space community (WAN) to scale back the round-trip-time (RTT). Moreover, within the occasion Cotoso2 deployed multiregional origin deployments, Azure Entrance Door makes use of well being probes to fetch content material from the least latent origin.

Furthermore, Azure Entrance Door additionally has SSL offload capabilities which may enhance efficiency additional. As well as, Azure Entrance Door is extremely optimized for HTTP and web-based purposes. With Azure Entrance Door, prospects are outfitted with varied layer 7 routing options. These options enable prospects to use enterprise routing and superior routing inside Azure Entrance Door. For instance, Azure Entrance Door can route requests to cell or desktop variations of Contoso2’s net utility based mostly on the shopper machine sort. Extra examples embrace SSL offload, path-based routing, quick failover, caching, and extra.

Right this moment Azure gives end-to-end options for each facet of utility administration. Azure Entrance Door gives seamless integration with different Azure companies similar to DNS, Net App, and Storage. These integrations enable prospects to simply create highly effective net purposes constructed utilizing the combination of a number of Azure companies.

Lastly, Azure Entrance Door gives built-in help for varied safety merchandise to assist defend prospects’ net purposes. For instance, prospects can safe their origins with layer 3, 4, and seven DDOS mitigation, and seamlessly allow Azure Net Software Firewall safety.

The following Image shows Azure Front Door connected to two backend regions, an active region, and a standby region. Within each region, there is an Azure Web app that is connected to various Azure services (Function App, SQL, Cosmos DB, and Azure cognitive search.  In addition, the image also showcases how static content is cached at the Azure Front Door level, which help with performance and reliability.

Buyer state of affairs 3—sustainable vogue retailor

Contoso3 is a big retail retailer centered on sustainable vogue objects. Contoso3 has a big on-line presence and has traditionally been internet hosting all their purposes on-premises. Nevertheless, given the benefit of the cloud and Azure, Contoso3 has begun migrating their purposes to Azure. One in all these purposes is their on-line retailer platform. Because the workforce at Contoso3 is evaluating completely different Azure world visitors distribution options, they’ve outlined a number of necessities that have to be addressed.

  • First, the workforce at Contoso3 will likely be doing a rolling migration the place a part of their utility will stay on-premises and the opposite half will likely be hosted on Azure. Any viable answer ought to be capable of direct visitors to on-premises servers to help this rolling migration plan.
  • Second, latency is essential for Contoso3 and shopper visitors must be routed to wholesome endpoints in a well timed method. 
  • Lastly, the answer wants to have the ability to direct customers to the right backend sort based mostly on their geographical location. Contoso3 caters to a variety of shoppers and sometimes has clothes objects particular to sure geographical areas.

With all the necessities said prior, Azure Site visitors Supervisor can be the optimum answer for Contoso3. With Azure Site visitors Supervisor, customers can add on-premises servers within the backend to help burst-to-cloud, failover-to-cloud, and migrate-to-cloud situations. As well as, Azure Site visitors Supervisor gives automated failover and multi-region help, which all end in visitors being served with low latency. DNS identify decision is quick, and outcomes are cached. The pace of the preliminary DNS lookup is dependent upon the DNS servers the shopper makes use of for identify decision. Usually, a shopper can full a DNS lookup inside roughly 50 ms. The outcomes of the lookup are cached throughout the DNS time-to-live (TTL). The default TTL for Site visitors Supervisor is 300 seconds (about 5 minutes). The Site visitors Supervisor may assist Contoso3 with their geofencing wants, particularly with the geographic routing characteristic. This characteristic will enable Contoso3 to direct customers to the right backend occasion based mostly on their geographical location.

The following image shows Azure Traffic Manager connected to three endpoints, where each backend endpoint is in a different region. When a user issues a DNS query with Azure traffic Manager, the DNS response is the endpoint closet to the user's location. A user can then directly connect to the endpoint given by the DNS response.


The next part discusses frequent use instances for every load balancing answer, and what every answer is optimized for.  

  Azure Entrance Door Azure cross-region Load Balancer Azure Site visitors Supervisor
Site visitors sort HTTP/HTTPS TCP/UDP DNS
Routing insurance policies Latency, precedence, spherical robin, weighted spherical robin, path-based, superior http guidelines engine Geo-proximity and Hash Primarily based Geographical, latency, weighted, precedence, subnet, multi-value
Supported environments. Azure, non-Azure cloud, on-premises Azure Azure, non-Azure cloud, on-premises
Backend Sorts Azure Software Gateway, Azure Load balancer, Azure Site visitors Manger Azure Load Balancer Azure Software Gateway, Azure Load balancer, Azure Site visitors Supervisor, Azure Entrance Door, Azure Cross Area Load Balancer
Session affinity X X NA
Website acceleration X NA NA
Caching X NA NA
Static IP NA X NA
Safety DDOS, Net Software Firewall, Non-public Hyperlink Community Safety Group Azure Useful resource Logs, Azure Insurance policies
SLA 99.99% 99.99% 99.99%
Pricing Pricing Pricing Pricing

Be taught extra

To study extra concerning the merchandise mentioned within the weblog please go to the next websites:



Please enter your comment!
Please enter your name here

Most Popular

Recent Comments