I was trying to read up on load balancing in Windows Azure, and all the information about it is extremely vague and non-specific. All I really want is a simple answer: how does Azure perform load balancing?
Many applications use sessions or in-memory data to increase performance. With Azure, I'm not sure if this is possible, because (from what I can tell), Azure doesn't have any sort of "sticky" sessions. Even if it wasn't session-based, but simply IP-based balancing, that would be enough for many applications.
So, the question of the day - how exactly does Azure perform its load balancing?
Load balancing refers to evenly distributing load (incoming network traffic) across a group of backend resources or servers. Azure Load Balancer operates at layer 4 of the Open Systems Interconnection (OSI) model. It's the single point of contact for clients.
Azure load balancers come in two varieties. There are public load balancers and internal load balancers, which are also known as private load balancers. A public load balancer is used when you need to load balance incoming Internet traffic to your virtual machines.
ILB is a security enhancement over the current public load balancing that is offered in Azure. It restricts the accessibility and creates a trust boundary between the load balanced Virtual IP address to a Cloud Service or a Virtual Network that doesn't require the public internet.
Ok to give a correct answer here - Azure DOES support load balancing in front of both web and worker roles (so the answer marked as best on this thread is completely wrong), but it does not support Affinity load balancing which is what jvenema was asking for I think. The current implementation uses round robin behaviour.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With