Likelihood to Recommend So a lot of companies that have a digital side and they have a lot of applications in the cloud, this is one of those areas that it can protect the net so it can lock 'em down, it'll build a baseline so you understand what that application's doing. So if it sees something not normal, it'll get protected against that.
Read full review [NGINX] is very well suited for high performance. I have seen it used on servers with 1k current connections with no issues. Despite seeing it used in many environments I've never seen software developers use it over apache, express, IIS in local dev environments so it may be more difficult to setup. I've also seen it used to load balance again without issues.
Read full review Pros Layer seven attacks are becoming far more common. Traditionally it was always layered three, layer four, where you get an additional firewall, but with the application layer attacks become more frequent, more popular, et cetera. So having the web application firewall protecting us, and then with the recent Log4j, that's the most recent use case when it gave us that instant level of protection whilst we remediated the Log4j that we had that and the F5 Distributed Cloud WAF was protecting us. I have a great relationship with the account manager, my account manager, and I think he drives the best price possible, um, for me, and I'm happy with that price. F5 Distributed Cloud WAF is always innovating and evolving. We run a very competitive proof value where we run numerous competitors against each other, and then we evaluate from that and then make the selection, and F5 Distributed Cloud WAF was the winner. Read full review 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)! Read full review Cons So we just had some performance issues when it comes to routing. Because the web application firewall sits in front of our website, which is hosted on-site, we had some trouble with the VGP protocols between the two sites and it took us a while to figure it out. So that is probably one area where we could improve. Otherwise, when it comes to the WAF functionality itself, it's really good. Read full review 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. Read full review Likelihood to Renew Great value for the product
Read full review Usability Front end proxy and reverse proxy of Nginx is always useful. I always prefer to Nginx in overall usability when you have application server and database or multiple application servers and single database i.e. clustered application . Nginx provides really good features and flexibility which helps the system administrator in case of troubleshooting and also from the administration perspective . Also, Nginx doesn't delay any request because of internal performance issues.
Read full review Support Rating John Reeve Principal, Lead developer, Lead designer
Read full review Alternatives Considered Basically,
Cloudflare is a more economical solution at the level of DNS balancing, easy to use with a few simple clicks and that has gained an advantage in the market, however, compared to F5, it falls short of the entire protection panorama that the solution provides since F5 does not It's just DNS that goes further and that's where it differentiates and stands out.
Read full review We have used Traffic, Apache, Google Cloud Load Balancing and other managed cloud-based load balancers. When it comes to scale and customization nothing beats Nginx. We selected Nginx over the others because
we have a large number of services and we can manage a single Nginx instance for all of them we have high impact services and Nginx never breaks a sweat under load individual services have special considerations and Nginx lets us configure each one uniquely Read full review Return on Investment Accelerated time to value as it was a requirement for a workload being provisioned on that cloud As an existing f5 customer, access to their solutions integrator (GridZero) made the sizing, licensing, purchases, and downloading of the software very quick and painless Read full review Nginx has decreased the burden of web server administration and maintenance, and we are spending less time on server issues than when we were using Apache. Nginx has allowed more people in our company to get involved with configuring things on the web server, so there's no longer a single point of failure ("the Apache guy"). Nginx has given us the ability to handle a larger number of requests without scaling up in hardware quite so quickly. Read full review ScreenShots