Currently, we're just using it as a load balancer. We haven't explored all the functionality yet, but we find it has too much to offer.

The ability to block constant requests for files that are not applicable to our VoIP deployment. We used to have a lot of 404s from our backend. Now they are blocked right up front.

We are not fully utilizing it. We are only responsible for load balancing. The most used and valuable is load balancing.

I can't speak to all of the HAProxy features because we don't use them all, but load balancing is very good.

HAProxy has a lot of features, so what's most valuable depends on what we are loading. The forwarding proxy is a valuable feature. HAProxy is a valuable product. 

The solution is open-source. 

HAProxy can provide protocol-level load balancing. We can use the HTTP or HTTPS load balancing, including the PCP and UDP protocol level load balancing.

The setup is straightforward.

It is scalable.

The solution is stable. 

It's saved project costs and time. Since the deployment is very easy and the open-source functionality saves a huge amount of cost in terms of project deployment.

Stability is number one. We have never had problems with it. When configured correctly, it could run for years. We never had a task that we could not achieve with HAProxy.

The most valuable feature of HAProxy is that its open source.

The most valuable thing for me is TCP/IP Layer 4 stuff you can do with HAProxy. You can go down to the protocol level and make decisions on something. 

The solution is user-friendly, works quickly and efficiently. 

The most important features would be the load-balancing of HTTP and TCP requests, according to multiple LB algorithms (busyness, weighted-busyness, round robin, traffic, etc). 

Another important feature that we cannot live without is the username/passwd authentication for legacy systems that had none.

Performance and SSL proxy/offloading capability. Compared to nginx it’s a lot cleaner and quicker.

• Reliability. HAProxy is the most reliable product I have ever used.
• It is stable. Period. Will not fail unless you do something wrong.

These features are why I give it a 10 out of 10.

Load balancing is valuable, and we are also using the WAF feature.

It is a complete open-source product. The good thing is that there is a lot of customization and development.

The most valuable feature is the TCP load balancing. It solves a problem for me where I can build files, not based on the health of the check, but rather the speed of the check. I found that functionality to be quite useful.

I have found HAProxy's flexibility to be most valuable. HAProxy is highly customizable and will meet the business demands of most companies. It comes with plenty of load balancing algorithms and can act as a forward and reverse proxy.

The solution is effective in managing our traffic. The integrations work fine. It's a load balancer. There's no need for complex integration. We hit it, and it balances the load in the servers that we assigned to it.

The anti-DDOS PacketShield filtering solution (embedded in the physical appliances) as well as the BGP route injection are great features and heavily used.

The firmware upgrades are extremely easy, fast and convenient. You only have to upload it and reboot. It is as fast and easy to roll back to the previous version.

These features are really an advantage over a "homemade" solution.

The ease of use of the configuration, and great documentation, are the most valuable features for us.

The VRRP redundancy is also a mission-critical feature that works seamlessly. I can bring down a server live with minimal downtime because of this.

Carers ACT operates a Skype for Business based call centre, which requires the use of a load balancer and reverse proxy for HTTP traffic for the front-end pools. HAProxy is able to fulfill both of these requirements.

In addition to these basic functions outlined above, Carers ACT also requires high availability and ease of configuration. HAProxy fulfills these additional requirements through providing high availability through VRRP and configuration synchronisation.

This product is scalable and inexpensive. 

The heavily tuned full stack (NIC, kernel, and user space) produces excellent performance. Their support is available for advanced troubleshooting.

It is easy to learn proxy operations. 

Performance.

Overall, it's a good solution.

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

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

Reliability and transparency are the most valuable features.

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

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.

Round robin and monitoring.

Load balancing, mainly. We are using two Apaches with HAProxy load-balancing.

Some people use HAProxy to load balance MySQL databases as well.

• Performance
• Stability
• Security
• Active health checks of back-end servers
• A lot of configuration options which let you deeply customize it.

Honestly, I have only evaluated the load-balancing feature because that is what I needed in my environment. As you can understand, for development and end-to-end testing, procuring a hardware load-balancer is a pretty expensive a deal.

• The Lua module to reach an increasing user base.
• HTTP/2 support
• Multi-thread support

• Load Balancing. We run large scale, backend infrastructure, serving millions of queries per second with low latency requirements.

With each new release, I find very useful features and love each addition. Recently, the seamless reload feature was much needed and very helpful.

The ability to handle a sequence of front- and back-ends gives the user the opportunity to send traffic through different services.

The feature that I have found the most valuable is that it works for my use case of application load balancing. I'm using it for PeerSense, and it's easy enough for PeerSense.