The main use cases are for load balancing and limiting traffic. It is utilized as a front-end server for balancing HTTP traffic, as well as for balancing traffic between application servers and database servers like Redis and Elasticsearch. HAProxy is employed for both HTTP and TCP load balancing purposes, ensuring optimal resource utilization and preventing overloading of any single server.
HAProxy Enterprise Ingress Controller
HAProxy TechnologiesExternal reviews
External reviews are not included in the AWS star rating for the product.
My proxy of election
Easy to use
Outstanding support
HAProxy for mission critical services
KubeCon review
I did talk to Frank Mancini about commented comments in open source haproxy.config not being included or handled. I'm OK with what it would take to convert it.
A versatile tool for load balancing and traffic management in different environments
What is our primary use case?
How has it helped my organization?
When dealing with scenarios that require splitting or monitoring Redis clusters with external masters and two slaves, HAProxy becomes essential. This is because HAProxy can significantly reduce delays in Redis communication when switching roles between servers. This reduction in delay improves application load time and prevents unnecessary downtime during server switchovers. It is a crucial tool in ensuring smooth service provision without any interruptions.
What needs improvement?
There is room for improvement in HAProxy's dynamic configuration. Currently, dynamic changes are lost when reloading the service, and it would be beneficial if dynamic configuration changes could be applied without losing the configuration or reloading the service, ensuring backups and preserving the static configuration.
For how long have I used the solution?
I have been using it for six years.
What do I think about the stability of the solution?
I would rate its stability capabilities nine out of ten.
What do I think about the scalability of the solution?
It provides impressive scalability. I would rate it ten out of ten.
How are customer service and support?
In a specific situation where a question was posted on a forum, the issue was successfully resolved within a day or the following day. I would rate their customer support services nine out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We worked with NGINX, but these two solutions are not entirely comparable as they serve different primary purposes. NGINX functions both as a web server and a reverse proxy server, while HAProxy is primarily a load-balancing proxy. They both have load-balancing capabilities, but their main focus and functionalities are distinct.
How was the initial setup?
The initial setup can be challenging. I would rate it six out of ten.
What about the implementation team?
For simpler cases, the deployment process can take around one hour. For more complex scenarios, it can extend up to one week.
What's my experience with pricing, setup cost, and licensing?
We are using HAProxy as an open-source.
Which other solutions did I evaluate?
NGINX is easier to configure and is well-suited for load balancing against an application server. However, HAProxy is more versatile and can be fine-tuned for various scenarios, particularly in load-balancing multiple application servers. In terms of deployment, HAProxy is easy to integrate into a green-blue deployment approach. It allows for simpler configuration and sending commands to its sockets.
What other advice do I have?
Based on customer stability and varying use cases, I recommend choosing this solution. I would rate it nine out of ten.
Useful tool in a Web stack
great balancing
Great personal and presentation.
Its amazing
Love it
Chars133
Maybe this survey
Chr abcdefgh