F5 BIG-IP DNS (formerly BIG-IP Global Traffic Manager) secures DNS infrastructure.
N/A
NGINX
Score 9.1 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…
Less appropriate: - Not best bet for startup’s as their budget is always tight - Not good for those companies where the engineers are not highly skilled otherwise the use Irules and security policies will not be utilised in optimal manner as it requires more cpu resources to work especially irules - For companies fully on cloud doesn’t best fit as I already highlighted cloud require more improvements when it comes to seamless performance Best Suited -Large enterprise companies where budget is not an issue - Companies whose traffic Rate Per Second is very high as it can handle huge RPS without latency - Companies whose business is surely depends on their availability
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.
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.
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.
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
Most important usability of F5 BIG-IP DNS is it’s stability which other vendors lack -As mentioned earlier as well, it’s scalability is humongous as it can honour millions of request per second without latency - irules feature makes it top and worthy to fight with top contenders like cloudflare and Cisco - Moreover it’s stable even when the Rate Per second is high and at the same time, DDos occurs - Interface is user friendly for simple tasks but requires more manual work - TAC should provide more assistance when it comes to normal support as well but they do offer professional support license for tasks which other vendor assist on normal license as well
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
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.
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.
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
Saved almost 1.2 million USD for one of critical activities as downtime could have posed this but due to failover based on health checks saved these bucks
Business impact which can be caused due to DDos attacks avoided
High cost licensing as mentioned earlier as well
Analytical limitations as F5 has also mentioned multiple it’s not an analytical tool
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.
