If a Linux user who is fairly good with Linux products takes care of HAProxy's installation part, it can be done easily.

It is possible to deploy the product within one to three hours with a fair amount of knowledge.

The product's deployment process is straightforward, as it can be easily managed with the help of HAProxy's document, which is available on its website. Users should be familiar with some Linux commands.

The solution is deployed on the cloud and on-premises models.

HAProxy is similar to engine NGINX, especially if you have a small company since you need only one or two people to take care of the deployment process. If you have a big enterprise, five to ten people are required to take care of the deployment phase.

The initial setup is fine. We just need to configure the solution. One good technical person is enough for the deployment. 

The initial setup is straightforward and took about two weeks to implement.

The initial setup is easy.

I would rate the initial setup a three out of five.

The initial HAProxy setup was straightforward. The setup is automated, which makes it instantaneous. 

The initial setup is very simple and straightforward. It's not too complex. 

One single administrator can manage and deploy this product.

The initial setup can be challenging. I would rate it six out of ten.

The deployment and configuration of HAProxy are not easy if we compare it with other solutions, such as F5. The full implementation took us one to two months to complete.

I rate the initial setup of HAProxy a three out of five.

The setup was pretty straightforward. When I started using HAProxy, I played around with it in a container and built from source, so I got a good feel for what it could do. And then I picked up a book called Load Balancing With HAProxy. After I read that, I felt confident I could use this service in a production setting. I was able to tune the knobs I needed to adjust and understand things pretty well. The book is pretty decent, but I wouldn't mind seeing a newer version of it. It was helpful. 

The HAProxy documentation on the web isn't bad, but the book is much nicer for me. I like to see how the authors apply HAProxy to specific use cases and leverage things. Also, they explain how to do something, whereas the documentation only tells you about the features and parameters. Sometimes it's hard for the documentation to show the importance of a feature and express how to do what you want. 

The initial setup takes a few minutes. We use Terraform to deploy and it's very fast. We have five users in the company. 

The learning curve is small if one is familiar with routing/networking in general, but it takes some time to fully understand the impact of some configuration settings. The support for all major Linux distros makes running and testing a breeze though.

Setting up an HAProxy is simple, however to run it in production you have to do a lot of tweaking.

Its initial setup is easy and not very complex. If you have a general understanding of how containers and VMware work, it is not very problematic to deploy it.

The initial setup documentation of HAProxy is good, but when you have to customize it for your application requirements, it gets difficult.

I found that the setup was pretty straightforward, although I had read a book on HAProxy before I started the project. I had given it some thought in terms of what it was that I wanted to do. The book that I read was good, and it was easy for me to install the product.

Only one person is required for deployment and maintenance.

Configuring our forward proxy was a little complex because it was my first time implementing such a solution. That being said, the people at HAProxy were more than willing to help me get the solution in place.

Straightforward, but received some help for the migration.

The initial setup was fairly straightforward. With a minimal configuration, you can get up and going quickly. However, it is very easy to modify the configuration to meet any requirements you may have, and reload in production with no downtime. The only complex part is having to maintain the base operating system, as HAProxy EE is simply a Linux package. The hardening of the operating system was done by myself since there is no appliance, like their ALOHA offering.

HAProxy is definitely a power-user tool. It is enormously scalable and flexible, but this can come at the cost of usability. For anything other than a simple topology, editing configuration files rather than using graphical tools will be required.

This, in itself, is not necessarily a bad thing, but rather for the scenarios that HAProxy excels, an administrator should have intimate knowledge of their environment and have undertaken appropriate planning. The ability to have very low-level access to configuration within each load balancer allows for configuration and deployments that could be limited by GUI configuration tools.

I have not currently used technical support.

The initial setup was trivial.

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.

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

The product is very simple to install and to use.

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 initial setup is pretty straightforward.

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

Easy to set up.

Complex, but their technical staff has made excellent progress on our migration to date.

It was straightforward. I created an Ansible playbook to install HAProxy. It is simple to install and the configuration files are easy to understand.

It was a little bit straightforward.