HAProxy Reviews

Our company used the solution as a proxy for Tanzu during an initial installation for conducting performance tests. 

It is easy to learn proxy operations. 

The solution has bad performance issues. 

I used the solution for six months. 

The stability is good and passed all tests. 

I did not need technical support. 

The solution is easy to install and configure in terms of the load balancer. Other tools might take eight days to install, but the solution only takes three or four days.

We installed the solution in-house using available documentation. 

Maintenance can be completed by one network administrator. Sometimes it is not easy to diagnose issues. 

The solution is open source so is free. 

We did not evaluate other options before the solution. We were not happy with the solution's performance so we switched to Load Balancing Analytics. 

The primary use case of HAProxy is for load balancing. 

This product is scalable and inexpensive. 

The visibility could be improved. Stability can falter when there is a lot of traffic. End-to-end connections are limited. 

Stability could be improved. 

The solution is scalable. 

The technical support is good, it's provided to us by the distributor. 

Licensing costs are inexpensive. 

I rate this solution six out of 10. 

Load balancing and SSL termination.

HAProxy enabled better performance at lower costs. That enabled us to provide more stability to our clients.

Performance.

A better GUI would be nice.

No issues with stability.

No issues with scalability.

Very professional, helpful.

We used F5 BIG-IP in the past and switchED due to performance issues and costs.

It is mostly straightforward and HAProxy was very helpful, guiding us during the deployment.

I think that the pricing is very fair, I would definitely recommend buying the Enterprise license.

Citrix Netscaler and Kemp LoadMaster.

HAProxy is a very powerful solution with great performance, but it needs to be evaluated carefully according to the specific environment and requirements.

We use it in a model teacher, project, and financial trading system.

Overall, it's a good solution.

We don't have a problem with the user interface. It's good.

We've changed solutions as it doesn't fit with our current needs. 

We have used the solution for a while, however, we are currently moving away from it.

We are currently moving away from it. We changed our orchestrator solution and we move to something else and now use an internal proxy.

We are end-users and customers. We don't have a business relationship with the solution.

I would rate the solution at a seven out of ten.

The cluster feature. I use it for my second informatic room.

Four days ago, I had an inundation in my informatic room, and there was no interruption of service, because HAProxy is an excellent cluster solution.

While the product is quite perfect, it could use more supervision and be more active. Also, more simplicity, more peripherals, and more scalability.

About five years.

Yes, the first time. I have an old VMware vCenter Server 6.0 . The VMware vCenter Server 6.0 cannot go with HAProxy. HAProxy developed a special feature for me to improve the function.

No issues. I have about 500 users on HAProxy, which use a web server and mail server.

No majors issues to contact them, but did contact them regarding questions about the product.

I have used before a server from Microsoft, and a server is very slow as a solution.

The product is very simple to install and to use.

Yeah, but I don't remember it, because the other product was very bad in comparison to HAProxy.

The product is very simple and fast. It's a microchannel.

Try it and if you like it, you buy it.

Reliability and transparency are the most valuable features.

This product is replacing another balancer which was not supported anymore. So, there is no major improvement for us.

In general, the improvement is in terms of the balancer sense which is moving from a single web server/single point of failure to using several back-end servers, that greatly improves the speed and reliable uptime.

I would improve the web-based UI, but it’s a matter of personal preference.

I have used this solution for one year.

There were no stability issues, it’s a stable product.

There were no scalability issues.

The technical support is very good , they are quick and responsive, which is essential for any product to succeed in this market.

Previously, we were using another product but it is no longer supported.

For the most part, the setup is pretty straightforward. However, as I mentioned earlier, thanks to the very good and quick technical support, all the complex requirements that we had were resolved quickly.

The pricing is good compared to the other similar products.

We evaluated at least four to five other products.

It’s a reliable product with good technical support.

We are using HAProxy for our internal load balancers between the front-end and back-end services. HAProxies are configured either manually (LVS redundancy included) or automatically (ambassador pattern by using a Consul & Consul-Template).

It reduced the load on our main load balancers.

• Flexible health-checking
• Good config format to auto-configure

We need to handle new connections by dropping, or queuing them while the HAProxy restarts, and because HAProxy does not handle split config files.

No stability issues.

No scalability issues.

We did not need technical support because the documentation is good.

The initial setup is pretty straightforward.

We use NGINX as well. However, because the health checks are a paid feature, I like to avoid it whenever possible.

We pretty much know all the software out there and its capabilities, so we did not evaluate anything else.

Use a split front-end and back-end instead of using the "listen" directive. Therefore, you are clear what you are setting up. 

Be aware of connections dropping during restarts, etc.

I'm using HAProxy in two use cases. 

The first is as an internal load balancer for OpenStack services, in private cloud solutions. So HAProxy is used in front of Galera (MySQL cluster), Nova API, and also in front of exposed docker services. 

The second use case is as a load balancer for a Web hosting solution. HAProxy is load balancing external traffic.

Configuration of HAProxy includes brute force sandboxing (including stick tables and hardcoded ACL for defined paths), splitting traffic by dynamic and static content to redirect it to the proper back-end, SSL, and HTTP headers management.

I can simplify configurations of many internal services (e.g. Web server configs) by moving some elements (like SSL) to HAProxy. I can also disable additional applications, like Varnish, by moving traffic shaping configurations to HAProxy.

Advanced traffic rules, including stick tables and ACLs, which allow me to shape traffic while it's load balanced.

Performance configuration options with threads, processes, and core stickiness are also very valuable.

In my opinion, there are three main areas to improve:

1. Make remote management more modern by adding API.
2. Propose a general HA solution for HAProxy (no I'm using keepalived for this).
3. Thread option should be a bit more stable.

No issues with stability.

No issues with scalability, but multiprocess config for HAProxy is more efficient than multi-thread.

I used NGINX in my Web environment. HAProxy has more traffic shaping options and it's a dedicated VNF load-balancer.

Initial setup was straightforward. The documentation is pretty thorough and up to date, and it is also easy to search.

During the implementation, you have to plan ACLs and back-ends first. That allows you to prepare a cleaner config.

I rate HAProxy a 10 out of 10. It is fast, flexible, and rock solid.