HAProxy vs. node-http-proxy

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.

Health checks and routing requests.

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

Load balancer

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.

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 load balance our ElasticSearch cluster using HAProxy. The health checks come in handy.

main load balancer.

Our SSL terminator and load balancer of choice

rabbitmq 의 로드 밸런싱 용도이자 celery 의 connection pooling 을 담당하기 위해 HAProxy 를 도입하여 사용하고 있습니다.

I used HAProxy as HTTP request dispatcher.

Balance traffic.

Load balancer

HTTPS termination and active/passive load balancing

High performance load balancer for the devices.

Doorman of choice

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

Load Balancing

HTTP load balancing in Vaultize private clouds.

MySQL (Percona) and Https Load Balancing

TCP proxy & load balancer for the MariaDB cluster

No need for this, for now