Google Cloud Load Balancing vs HAProxy: What are the differences?
Developers describe Google Cloud Load Balancing as "A global load balancing on Google's worldwide network". You can scale your applications on Google Compute Engine from zero to full-throttle with it, with no pre-warming needed. You can distribute your load-balanced compute resources in single or multiple regions, close to your users and to meet your high availability requirements. On the other hand, HAProxy is detailed as "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.
Google Cloud Load Balancing and HAProxy can be categorized as "Load Balancer / Reverse Proxy" tools.
Instagram, Dropbox, and Medium are some of the popular companies that use HAProxy, whereas Google Cloud Load Balancing is used by Evernote, PointsHound, and BetterCloud. HAProxy has a broader approval, being mentioned in 602 company stacks & 1060 developers stacks; compared to Google Cloud Load Balancing, which is listed in 11 company stacks and 4 developer stacks.
What is Google Cloud Load Balancing?
What is HAProxy?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Google Cloud Load Balancing?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Google Cloud Load Balancing?
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.