HAProxy Community Edition vs. NGINX Plus

It prevents a single server failure from being a downtime event by adding redundancy to every layer of your architecture. A load balancer facilitates redundancy for the backend layer (web/app servers), but for a true high availability setup, you need to have redundant load balancers as well. So it is well suited for all production related servers and less suited for individual servers that do not require redundancy.

Incentivized

Makes our life easy as application admins in securing our applications and making them accessible. We can easily add an application within a few minutes and define the backend servers right away.

Incentivized

• Low-Cost Load Balancer
• Intelligent Request Routing based on URL and/or URI
• Extremely flexible load balancing and healthchecks, can do almost anything including HTTP, HTTPS, PostgreSQL, etc.
• SSL Termination

Incentivized

• APIGW
• Policy Enforcement
• Centrally Manage API Traffic

Incentivized

• A few, rare times each year, HAProxy CPU utilization spikes to 100% and server has to be rebooted - this may be related to HAProxy OR it could be an external factor causing this.

Incentivized

• An AI bot would be cool to help build config files
• More webinars for advanced NGINX Plus would be great
• GUI tool... might already be one available

Incentivized

No reason not to renew it, we are happy with it.

Incentivized

It is very easy to use. I was able to find a lot of documents for it on the internet. Very good community support. There are lots of examples available to try. We mostly use a command-line user interface to interact with it. The CLI is also super easy to use and very easy to interact with

Incentivized

Very easy to use

Incentivized

We haven't used customer support. We mostly used the community version. We build a multi-node HAProxy cluster with HA to the proxy itself using opensource plugins available. With the support available on the internet and the documents available we don't need to use much customer support.

Incentivized

We had an issue after upgrading from RHEL 7 to 8, and there were some issues that the security team imposed upon the platform with a scanning tool. We also had a VXLAN environment that was not properly sending a gratuitous arp to the network. NGINX support was instrumental to speedily resolving our issue.

Incentivized

We chose HA Proxy because it is cheaper than a hardware balancer, it is an open-source solution with a large community behind it and with constant updates. It also allows custom scripts according to needs.HA Proxy is a solution used in many internet sites like GitHub, Reddit, Twitter, and Tuenti.

Incentivized

The API and dashboard alone make NGINX Plus a better choice.

Incentivized

• Significantly lower investment vs competitors. In the case of F5s we have Virtual Editions so we're paying for the hardware to run it on top of the several thousand dollar licenses that are required for each pair and we currently have a pair of F5s per client so there's a huge potential for cost savings there.
• Requires our network engineers to learn a new skill or our Systems engineers to take on the responsibility of managing the load balancers. It's not a huge difference either way, but it does impact the way we have done business in the past.

Incentivized

• We are planning by using NGINX it can greatly reduce our OPEX by 50% "just our own running APIGW" the cascading effects in the long run will be much more.

Incentivized