Azure Container Service vs HAProxy: What are the differences?
Developers describe Azure Container Service as "Deploy and manage containers using the tools you choose". Azure Container Service optimizes the configuration of popular open source tools and technologies specifically for Azure. You get an open solution that offers portability for both your containers and your application configuration. You select the size, the number of hosts, and choice of orchestrator tools, and Container Service handles everything else. 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.
Azure Container Service can be classified as a tool in the "Containers as a Service" category, while HAProxy is grouped under "Load Balancer / Reverse Proxy".
"Easy to setup, very agnostic" is the primary reason why developers consider Azure Container Service over the competitors, whereas "Load balancer" was stated as the key factor in picking HAProxy.
According to the StackShare community, HAProxy has a broader approval, being mentioned in 452 company stacks & 205 developers stacks; compared to Azure Container Service, which is listed in 8 company stacks and 7 developer stacks.
What is Azure Container Service?
What is HAProxy?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Azure Container Service?
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.