It is much more flexible than a firewall since it gives you great logging and then control of what is let through to the WAF.

Having the right load balancing solution – which is what HAProxy is – and protection in place gives organizations peace of mind. 

It helps include the reverse proxy or more security modules for enhancing security. It helps with enhancing web application security.

We are using HAProxy, for secondary loads and use cases. There are times that our customers require specific static IP addresses versus AWS CloudFront, which uses IP pools. So when we have such environments, we use HAProxy for SSL termination and load balancing.

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.

As our traffic began increasing nine years ago, we desperately needed to load-balance TCP requests (for DBs). We originally used round robin on an array[] which stored the IPs of half a dozen DBs. But with HAProxy, we didn't need to maintain such complexity. We later exploited many more features.

Software defined load balancing allows us to dynamically adjust and codify routing decisions. This speeds up development.

In some environments we are handling millions of requests per minute in a high-availability HAProxy cluster. I don't know any other free software that can do that, from a performance perspective.

It made something possible where I do load balancing on a container, without having to configure it at the firewall.

HAProxy has assisted us with bringing legacy systems in compliance with third party security requirements.

We needed a simple proxy system that is open source. HAProxy was the most used tool for any issues that we ran into. We did not want to use something that was not used much so that we could fix the issues that came up.

It makes the hosting on multiple platforms/datacenters very easy, without having to worry about the high availability required by our customers.

I estimate that this product has saved our company hundreds, if not thousands, of dollars in possible downtime from previous load balancers. We make a lot of our money from online sales, so it is critical to have 99.9% uptime.

One of the core services that Carers ACT provides carers within the ACT region is both an advisory and respite support telephone service. Carers use this service to be connected to services, access both advice and support, as well as accessing respite services to assist them in their caring role. The Carers ACT Skype for Business implementation is being progressively re-architected to remove single points of failure, of which the load balancing role was one.

Carers ACT is also exploring innovative approaches to delivering services to carers who are unable to physically attend events, such as live streaming and providing online face to face contact. These new approaches are likely to be supported by the Carers ACT Skype for Business infrastructure. The implementation of the HAProxy load balancing solution will allow Carers ACT to begin to deliver these new services.

We have been able to achieve extremely high performance load balancing in a short amount of time. As an example, using L4 mode, we routinely return more than 100 gigabytes per second of MySQL traffic, from a cluster of about 10 replicas.

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

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.

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.

It reduced the load on our main load balancers.

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.

We were able to use HAProxy for round robin with our databases, or for a centralized TCP connection in one host.

Four to five years back, we were struggling with Web load-balancing; we were facing issues with a single Apache. We got the best, and open-source, solution.

It has allowed us to evenly distribute the load across a number of servers, and check their health and automatically react to errors. It also allows us to do graceful reloads, so not a single request is lost.

It has been a great help for all the use cases noted above, and economical.

It improves our scalability and responsiveness services to meet our demanding customer requirements. We now have much better metrics regarding clients types.

We expect to see the following improvements:

• Software LB that can run on commodity hardware, on enterprise grade Linux OS distributions.
• Simplifies our operations, improves our scalability, and lowers our costs.
• Open Source, with an established community of users that we can leverage to operate and grow our deployments.

Layer 7 health checks improved stability. Logs and metrics are very rich and easy to export which makes it easier for us to pinpoint once something is not working as we expect.

With an OpenShift environment, HAProxy gives us an easy way to handle a lot of containers.