HAProxy Community Edition is a free, open source reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is presented as suited for very high traffic web sites.
$0
Kemp LoadMaster
Score 8.9 out of 10
N/A
LoadMaster from Kemp Technologies in New York is an application delivery controller.
$1,720
per year
NGINX
Score 9.2 out of 10
Mid-Size Companies (51-1,000 employees)
NGINX, a business unit of F5 Networks, powers over 65% of the world's busiest websites and web applications. NGINX started out as an open source web server and reverse proxy, built to be faster and more efficient than Apache. Over the years, NGINX has built a suite of infrastructure software products o tackle some of the biggest challenges in managing high-transaction applications. NGINX offers a suite of products to form the core of what organizations need to create…
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, …
Setup is easier and more straight forward on the Kemp. While I am a technical person and can setup HAProxy for the client's needs, it would be difficult for the client to manage the configuration themselves.
When we looked at other load balancers, we ran into some issues. For some of the free ones, these don't necessarily perform as well - which is probably why they are free. When looking at some of the other brands, some are too complicated to use - they may have a ton of advanced …
Nginx's cache mechanism is better than Apache and HAProxy. Also Nginx is very light weight and works for multiple sites with much less work. i.e. As front end proxy server configuration is very easy as compared to other applications. Apache sometimes crashes and is not able to …
NetApp, f1, etc., [I've] used them all. I find using commodity hardware across diverse endpoints running software solutions is cheaper while being more available than individual hardware solutions. and I find Nginx to be the best proxy solution that can do everything we need.
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.
Loadmaster is very powerful and flexible load balancer. Variety of options allows to create a complex network of rules and routes. During our website rollout Loadmaster allowed us to run multiple generations of the website simultaneously and seamlessly by doing the content switching on the fly. Powerful API allows easy integration into any development lifecycle.
Nginx is well-suited for any web server scenarios, such as web applications, backend or reverse proxy for both application and HTTP requests, and distribution. It is less appropriate for Windows-based applications that run directly on a Windows Server host. In any case, it is very easy to manage, through separate conf files for each application or site you want to host with it.
Where the LoadBalancer excels is the multiple levels at which you can load balance servers. We currently use layer 7 LB, but others are available as well.
I particularly like the ability for the LB to know when servers are down, and if all are offline then you can create a redirect to a static HTML page or some other destination that is more informative.
The ease in which a service can be created and deployed using already pre-canned templates makes it a very convenient setup process.
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.
Customer support can be strangely condescending, perhaps it's a language issue?
I find it a little weird how the release versions used for Nginx+ aren't the same as for open source version. It can be very confusing to determine the cross-compatibility of modules, etc., because of this.
It seems like some (most?) modules on their own site are ancient and no longer supported, so their documentation in this area needs work.
It's difficult to navigate between nginx.com commercial site and customer support. They need to be integrated together.
I'd love to see more work done on nginx+ monitoring without requiring logging every request. I understand that many statistics can only be derived from logs, but plenty should work without that. Logging is not an option in many environments.
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
Kemp makes it very easy to setup, configure and manage the LoadMaster without needing a lot of help from their engineers. The interface is very easy to understand and intuitive to use. We like how it is not complicated - I can easily have one of my techs login and they can figure out how to setup/configure virtual services for load balancing without needing a manual or tech support.
This tool is really easy to use and configure. Consumes very less system resources. It is highly modular and configurable. You can easily use it with other tools like certbot for SSLs. You can configure basic security with configuration and headers
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.
Support has been easy to deal with; I have only need[ed] to contact them a few times during setup. Once its been in place and operational, we have not need[ed] to mess with the system [which] is a huge advantage. I like system[s] that do not break and require constant attention in a production environment.
Community support is great, and they've also had a presence at conferences. Overall, there is no shortage of documentation and community support. We're currently using it to serve up some WordPress sites, and configuring NGINX for this purpose is well documented.
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.
We chose Kemp LoadMaster because it is 1/10 the price of the competition and MUCH easier to deploy and configure and WORKS. We have had ZERO issues with the product since installation. Their engineers and their sales team have both reached out post-install to check in and see if everything is working as expected.
I have found that [NGINX] seems to perform better throughout the years with less issues although I've used Apache more. I would definitely recommend [NGINX] for any high volume site and I've seen this to usually be the case from most provided web hosts who will pick [NGINX] over alternatives
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.
We used Kemp LoadMaster for many projects. For a lot of customers, load balancers were too expensive or too complicated before we introduced Kemp products.
It's not a overly complicated product, so we were able to train many engineers on it and have them get a certification.
By using Nginx, we can host multiple web services on a single server, keeping our infrastructure costs lower.
Nginx maintains our HTTPS connections, allowing us to keep our promise to our customers that their data is safe in transit.
Due to Nginx's extremely low failure rate, our web addresses always return something meaningful, even when individual services go down. In sense, this means we are "always online" and allows us to maintain brand and support our customers even in the face of catastrophe.