I use the solution in my company for TCP streams. I have not used the product for web servers like Apache and NGINX. I have used the product for SMTP and SMPP protocols. I also used the tool for email services and POP3 servers. HAProxy handles the area where traffic has to be forwarded from one port to another very well.

We use it as a load balancer for our application servers, including Bonita, VPMN, our NAS reporting tools, and Telus solutions. We have two or four applications in the back end and use HAProxy as a load balancer.

The primary use case of this solution is to control the IP addresses accessing our devices and and blocking invalid requests to our back end servers.

For production purposes, we use HAProxy, which is a web application.

Our primary use case is load balancing.

We primarily use HAProxy for the load balancer. 

The product is an open-source load balancer. We deploy it for our application as a front-end server where all the users come on that particular HAProxy server, and it is redirected to our back-end servers.

HAProxy has been our primary SSL termination technology in production. We use it for our own product, which is Qivos Cloud. It is a software service and we used HAProxy for high-traffic API gateways. These products load balance our servers.

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. 

We are using HAProxy for load balancing.

I use it for managing Redis clusters where I have a front-end for a read-write and a front-end for a read-only. I have no idea who else in my company uses it. I had opted to use this because we have silos in our company. We have a network silo that does the load balancing, and I wanted to control how these tests worked with the load balancing. I wanted them to do load balancing where they hand off like a TCP Fast Open. They perform a check on these services with TCP Fast Open.

For example, there is one free HAProxy service for each node, and they use TCP Fast Open for things like that. It's flipped to the HAProxy, and then they establish a persistent connection. It's more of a hand-off, and then I can do all the magic. You can do most of the things I'm doing with HAProxy in F5 too. However, it's siloed off and takes a long time to get things done. I don't have any agility. I took that upon myself with HAProxy because it's a lot quicker to do it myself instead of waiting weeks for somebody else to do it.

We use the open source version in our dev environments, and the commercial product for production and pre-production. Our primary use case is for reverse proxy, especially for switches in the different environments. I am a system engineer. 

We have the following use-cases for HAProxy:

1. To load-balance dozens of Apache 2.4 Servers mod_proxy. (Internal load-balance Tomcat, Jetty, JBoss app containers, using TCP load-balancing).
2. To load-balance hundreds of MySQL and PostgreSQL databases using TCP load-balancing. We manage inventory of these through Ansible automation.
3. To provide a layer of security (username/passwd) authentication for legacy back-end Web apps that may not have username/passwd implemented yet. Some financial Web apps were created over 15 years ago and focused on reports, files, logs, and market share stats and were written in Perl. We also had a very old Kibana interface to visualize those logs. Such Web apps required HAProxy to tunnel the requests with un/pw authentication.
4. To redirect traffic internally based on /URL to the relevant services (DNS nameserver) and as a gateway to tunnel traffic to customers who explicitly require reverse-IP authentication. The DNS nameserver was a trendsetter that we learned quickly and now cannot live without.

E2E load balancing of Layer 7 and Layer 4 applications.

We are just using this product in our UAT environment.

Our primary use for this solution is to mount service for Redis.

The solution is used for high availability. We use it for the backend to distribute the load.

Load-balancing between hosting sites, using Level 4 and Level 7 (with proxy-protocol, depending on the requirements).

Our primary use case for this solution is to perform Layer 7 load balancing/reverse proxying of both our internal and external web applications.

We also use it for SSL offloading, and are beginning to utilize the basic Web Application Firewall functionality of it. 

HAProxy also performs VRRP, for redundancy, in case one of the servers were to go down.

The primary use case of HAProxy is for load balancing. 

I use HAProxy for individuals who can not buy low balancers. I built NFV in a box and send individuals a pathway into an HAProxy VM.

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

Load balancing and SSL termination.

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

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).

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.

In my previous company, we had a lot of connections with carriers and we had this communication centralized with HAProxy. We had a high-availavility environment with HAProxy, and Keepalived too for database connections.

I am using HAProxy on a live production Web Server (Apache load balancing). It's a very good open-source solution.

Proxying the requests for our API to a number of back-ends. We are using it in Linux with Keepalived to ensure high availability.

Primary use case of this solution is during PoC, demos, and in development environments. I have found HAProxy very helpful in replicating production environment architecture in a development and testing environment.

It serves as a fast front-end solution to our services.

Also, it uses the mobile detection module that I developed and maintain.

HAProxy is used both as an external (customer facing) and internal (between service APIs) solution. We use it for SSL offload, domain and path based ACLs, request header manipulations, and much more.

We are using it for application load balancing.