NGINX vs. Radware Bot Manager

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

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

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

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

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.

• 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

• Network Bandwidth efficiency

Incentivized