We are serving websites and Web Apps on Azure.
Should we be using an Application Gateway or Load balancer?
Our existing Set up: We have an ARM v2 Resource Group with a VNET, SUBNet, Availability Set, 5 WIN2012 R2 VMs, 5 NICs,(Currently behind an Azure Load Balancer)
Should we consider using an application gateway instead of a load balancer?
We are trying to achieve an even distribution of traffic load across the 5 VMs:
FYI: The 5 VMs are synced to serve the same content
All 5 VMs are currently serving eg www.website1.com,www.website2.com, www.website3.com This is replicated across all 5 VMs
In an ideal world the Application Gateway/Load Balancer would distribute the traffic across the 5 VMs as evenly as possible
We typically have 100s of multiple concurrent users, sometimes 10,000s at peak periods.
In an ideal world we would evenly split those users across the 5 VMs thus evenly distributing the worker processes. (I understand this is an ideal as sessions can vary in length and intensity)
All of our services are stateless. Currently we store cookie info client side, or, in various databases
I am assuming that having some form of session affinity is good practise on either an appication gateway or load balancer?
Should we consider using an application gateway instead of a load balancer?
Thanks for your help in advance
Colin