We use HAProxy to load balance between our webservers. It balances TCP between the machines round robin and leaves everything else to Node.js, leaving the connections open with a reasonably long time to live to support WebSockets and re-use of a TCP connection for AJAX polling.

I use an Application Load Balancer to balance the load to the EC2 clusters of nightly.zerotoherojs.com and dojo.zerotoherojs.com.

Addditionally, ELB protects my cluster against DDOS attacks: So it is multi-birds with one stone.

HAProxy manages internal and origin load balancing using KeepaliveD. Two small servers host the entire site, never moving about 15% load even during the largest load spikes.

We use HAProxy to balance traffic at various points in our stack, includgin nginx nodes on different physical machines, and api nodes on the backend.

I use HAproxy primarily for application routing and SSL termination. I also use its logs and statistics to visualize incoming traffic in Kibana.

We use HAProxy to load balance web requests for our web application, but also for some internal load balancing of microservices.

We're progressively migrating from classic ELB to newer ALB for ssl offloading and NLB for internal load balancing.

AWS ELB is used to load balance various web and application services across multiple EC2 instances.

• Application type
• SSL free
• forwarding by rules.
• multiple target groups with only one ALB

For balancing the presentation tier, and for SSL offloading (which is great for performance.)