DigitalOcean Load Balancer vs HAProxy: What are the differences?
What is DigitalOcean Load Balancer? Scale your applications and improve availability across your infrastructure in a few clicks. Load Balancers are a highly available, fully-managed service that work right out of the box and can be deployed as fast as a Droplet. Load Balancers distribute incoming traffic across your infrastructure to increase your application's availability.
What is HAProxy? The Reliable, High Performance TCP/HTTP Load Balancer. HAProxy (High Availability Proxy) is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
DigitalOcean Load Balancer and HAProxy belong to "Load Balancer / Reverse Proxy" category of the tech stack.
According to the StackShare community, HAProxy has a broader approval, being mentioned in 457 company stacks & 211 developers stacks; compared to DigitalOcean Load Balancer, which is listed in 3 company stacks and 7 developer stacks.
What is DigitalOcean Load Balancer?
What is HAProxy?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose DigitalOcean Load Balancer?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using DigitalOcean Load Balancer?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
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.
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.