NGINX vs. Radware Bot Manager

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

Incentivized

All new upgraded non-human bot detection feature is widely used across all the platforms open for customers and it is a great success. It provides zero access to malicious bots.

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

• ShieldSquare provides an easy to implement way of identifying website users that could be bots.
• By rating the potential of the user of being a bot, we are able to handle that user in the proper way.
• False positives are extremely rare with ShieldSquare. Plus, their support staff is also available to analyze traffic to specific content, and they can customize their algorithms when necessary to optimize the performance of their solution to suit our needs.

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

• It would be nice to allow for more granularity when selecting which bots I'd like to allow through. I contacted support and asked about this and they said this was in the works.
• If you select to show captchas instead of blocking, I feel their captcha screen could use some improvement on the UI/UX to make it more intuitive for users to know what to do. I contacted support and made them aware of this.
• Would be nice to see captchas information in the statistics (i.e. how many captchas were presented, from what IP addresses, how many were filled out correctly),

Incentivized

Great value for the product

Incentivized

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.

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

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

Incentivized

When I compared these two products, Distil Networks only offered a solution where their bot detection sits in between your website and the visitors, similar to how Cloudflare works. I didn't want this so I decided to go for ShieldSquare that uses connectors. I want my visitors to hit the website directly, not have something sit in between.

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

Incentivized

• Network Bandwidth efficiency

Incentivized