HAProxy Community Edition vs. NGINX vs. SolarWinds IP Address Manager (IPAM)

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

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.

Incentivized

SolarWinds IP Address Manager is very useful the bigger and more complex the environment. Smaller organizations will have to consider the cost as it provides little benefit over monitoring maybe 2-3 servers. But I have over 24 DHCP servers with on average 15 subnets each so tracking and monitoring all that was very time-consuming. As a result, it was generally ignored until there was an issue. With SolarWinds IP Address Manager, I was able to set alerts to monitor scope utilization and duplicate IP addresses.

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

• Very low memory usage. Can handle many more connections than alternatives (like Apache HTTPD) due to low overhead. (event-based architecture).
• Great at serving static content.
• Scales very well. Easy to host multiple Nginx servers to promote high availability.
• Open-Source (no cost)!

Incentivized

• With IPAM automated address scanning, we can be confident that we are looking at an up-to-date, accurate snapshot of our network.
• The built-in alerts are a great safety net. We know that even if we aren't paying close attention to our IP address space, IPAM is. If a range is nearly full, IPAM lets us know before it becomes a real problem.
• IPAM's event logging gives us insight into any and all changes made by our network engineers.

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

• 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.

• The user experience is not as intuitive as other products. We have to be more restrictive around level 1 help desk access compared to NCM or NPM in SolarWinds.
• Making and enforcing changes, not just monitoring, has been hit or miss in some instances.

Incentivized

Great value for the product

Incentivized

We are heavily invested in SolarWinds. We currently own Network Performance Monitor, Netflow Traffic Analyzer, User Device Tracker, Server Application Monitor and Network Configuration Manager. We have NOC mode setup for deskside support for monitoring any down devices that may effect our network across the globe. This application gives us the information we need when we need 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

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

Incentivized

SolarWinds IPAM is like what SolarWinds itself says, i.e. easy to use and simple. SolarWinds has really made their orion and non-orion platform products so simple that any newbie can give a try and make the best use out of it. I learned SolarWinds IPAM by myself in a POC environment, and not just IPAM but other modules and now I own 6 certifications. You see how easy to use this product is.

Incentivized

We don't have any issues with availability. Our cluster setup provide us a 99,9% availability that is enough for us.

Incentivized

We do not integrate IPAM into other systems other than the standard Orion integration. The performance is reasonable, however, we are running all the SolarWinds applications on a very large server.

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

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.

Incentivized

I have not contacted customer support and therefore have no experience in this area. I know we have some issues with our VAR support at this time for Orion, but I don't know if the IPAM falls into the same support structure. Perhaps others in the organization may know more regarding the support area.

Incentivized

Know the full scope of what you will be installing. Solarwinds can be a very complex installation. IPAM is just one fairly simplistic piece.

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

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

Incentivized

SolarWinds IP Address Manager was cheaper than both alternatives and far easier to manage. Device42 interface is years behind what Solarwinds offers. It is very outdated; BT Diamond required remote management and we constantly had to message support, it reached a point where it was better not to have the product at all.

Incentivized

We have not experienced any scalability issues with this product. However, SolarWinds needs to allow users to scale horizontally without any license restrictions. For example, we would like to separate Netflow and Orion onto different platforms but are unable to due to license restrictions.

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

• 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.

Incentivized

• IPAM has saved countless hours of running scripts and gathering data to compile reports to plan re-subnetting globally.
• IPAM has reduced helpdesk incidents by immediately spotting bad DNSR and IP conflicts.
• IPAM has helped eliminate blocks on projects whereas there is not currently enough address space requiring major changes to accommodate more IP'ed servers, gear, etc.

Incentivized