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
SUSE Linux Enterprise Server
Score 8.4 out of 10
N/A
The SUSE Linux Enterprise Server is distribution of the Linux operating system originally developed in Germany.
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.
We use it for every linux service we need to have running. It really works great and is easily manageable with the SUSE Manager, which helps a lot with the updating process. Although it is not stressfull on the CMD itself, it really does simplify things. Besides that, we are really happy with working with SUSE Linux Enterprise Server.
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.
The support window for service packs after a new SP is released is too short.
Community engagement is low.
There are times when supported packages fall too far behind and create compatibility issues with applications. The Open Build Service usually provides a way around this, though.
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
We've been using this OS for about 8 years in a productive environment. During this time, we have never run into any problems that stopped or impacted our production environment. We have been able to solve any problem we ran into using either common sense, suse documentation or suse support.
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 personnel are helpful and fairly fast to bring resolution to non-emergency issues. Patches are created and posted in a timely fashion. We so far have not had any major problems that needed support
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 went straight to SLES when we initially started migrating oracle to hana since at that time, HANA came on a pre-installed server that had to be purchased from an official vendor, and SLES was the only allowed OS. We stuck with SLES after we became certified to do our own installations because so far, SLES was a good fit for us.
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.
