F5 BIG-IP DNS (formerly BIG-IP Global Traffic Manager) secures DNS infrastructure.
N/A
HAProxy Community Edition
Score 9.3 out of 10
N/A
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.
It's well suited. Like I said, it provides us, it provides the clients and the business environments throughout an Internal Revenue Service. The network visibility needed for them to provide their application and the use of their applications throughout the Internal Revenue Service and the enterprise, as far as IRS.
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.
I'd like to see better reporting capabilities on the decision-making process for DNS resolutions. Currently there are plenty of log messages for that, but I'd like to see tighter integration into the GUI.
It could be an improvement to better discriminate features intended for AA vs LDNS functionality within the GUI.
My understanding is a lack of support for UDP traffic
One mistake in the haproxy.cfg prevents the entire thing from starting rather than only affecting the part of the config file that may have a typo of some other syntax problem.
We use this heavily and it is one of the best products out there for this type of use case. We already have LTMs and to leverage GTM on top of that is just a piece of cake. Everything is so well integrated its amazing
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 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.
As I mentioned, the GSLB capability, being able to do intelligent DNS by having access to monitor specific endpoints associated to my current BIG-IP infrastructure, I believe that brings a huge value, then combine fast responses and security.
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.
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.
