question

AnkitRathod-6794 avatar image
0 Votes"
AnkitRathod-6794 asked SaiKishor-MSFT edited

Azure Front Door Backed Pool Type || Azure Load Balancer

i have Azure virtual machines that are deployed to three different Azure regions. Each region has a single virtual network that contains three Azure virtual machines that are part of the same subnet. An application currently resides on the virtual machines that are accessible via HTTPS. Currently the machines are not accessible from the Internet. I'm Planning to use the Azure Front Door service to load balance the requests for the application across the virtual machines.

Can I use Azure Private Load Balancer or Public Load Balancer or Something else and please explain Why ?

azure-front-doorazure-load-balancer
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

SaiKishor-MSFT avatar image
1 Vote"
SaiKishor-MSFT answered SaiKishor-MSFT edited

@AnkitRathod-6794 Thank you for reaching out to Microsoft Q&A.

I understand that you want to setup Azure Front Door with Azure Load Balancer to load balance traffic to your application in multiple VMs in different regions.

You can defintely use Azure Load Balancer to Load Balance traffic to multiple VMs hosting this application.

A 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. Public Load Balancers are used to load balance internet traffic to your VMs.

An internal (or private) load balancer is used where private IPs are needed at the frontend only. Internal load balancers are used to load balance traffic inside a virtual network. A load balancer frontend can be accessed from an on-premises network in a hybrid scenario.

You can also consider using an Appkciation Gateway for Load Balncing between the VMs as it has additional features.

Azure Application Gateway is a web traffic load balancer that enables you to manage traffic to your web applications. Traditional load balancers operate at the transport layer (OSI layer 4 - TCP and UDP) and route traffic based on source IP address and port, to a destination IP address and port.

Application Gateway can make routing decisions based on additional attributes of an HTTP request, for example URI path or host headers. For example, you can route traffic based on the incoming URL. So if /images is in the incoming URL, you can route traffic to a specific set of servers (known as a pool) configured for images. If /video is in the URL, that traffic is routed to another pool that's optimized for videos.

Here is a link that talks about different Load Balncing options available within Azure.

Hope this helps. Please let us know if you have any further questions and we will be glad to assist you further. Thank you!

Remember:

Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.

Want a reminder to come back and check responses? Here is how to subscribe to a notification.




5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.