What users are saying about
93 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>Score 9.2 out of 100
Based on 93 reviews and ratings
14 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>Score 7.2 out of 100
Based on 14 reviews and ratings
Feature Set Ratings
Application Servers

7.9
NGINX
79%

WSO2 API Manager
Feature Set Not Supported
N/A
NGINX ranks higher in 6/6 features
NGINX ranks higher in 6/6 features
IDE support

8.0
80%
1 Rating

N/A
0 Ratings
Security management

8.0
80%
3 Ratings

N/A
0 Ratings
Administration and management

6.3
63%
3 Ratings

N/A
0 Ratings
Application server performance

9.0
90%
3 Ratings

N/A
0 Ratings
Installation

7.3
73%
3 Ratings

N/A
0 Ratings
Open-source standards compliance

8.5
85%
2 Ratings

N/A
0 Ratings
API Management

NGINX
Feature Set Not Supported
N/A

5.1
WSO2 API Manager
51%
WSO2 API Manager ranks higher in 7/7 features
WSO2 API Manager ranks higher in 7/7 features
API access control

N/A
0 Ratings

8.0
80%
2 Ratings
Rate limits and usage policies

N/A
0 Ratings

8.0
80%
2 Ratings
API usage data

N/A
0 Ratings

1.0
10%
2 Ratings
API user onboarding

N/A
0 Ratings

4.0
40%
2 Ratings
API versioning

N/A
0 Ratings

9.0
90%
2 Ratings
Usage billing and payments

N/A
0 Ratings

5.0
50%
2 Ratings
API monitoring and logging

N/A
0 Ratings

1.0
10%
2 Ratings
Attribute Ratings
- NGINX is rated higher in 1 area: Likelihood to Recommend
Likelihood to Recommend

9.2
NGINX
92%
27 Ratings

5.0
WSO2 API Manager
50%
2 Ratings
Usability

9.0
NGINX
90%
1 Rating

WSO2 API Manager
N/A
0 Ratings
Support Rating

8.1
NGINX
81%
8 Ratings

WSO2 API Manager
N/A
0 Ratings
Likelihood to Recommend
NGINX
[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.
Sr. Software Engineer
Tempus Labs, Inc.Computer Software, 1001-5000 employees
WSO2 API Manager
It's free! No argument can win a fight with that! And it's the only reason I gave it a 5. If you have no money to spend, and a simple environment you'll have a nice product. But free does come with a price. After 5 years we're still struggling with ports, and analytics (it just won't work without any errors caused by some configuration somewhere). An API Manager should work out of the box. The only configuration expertise that any developer wants to invest in, is the configuration of API's. Not the product itself... Anyone who've seen the training material, just for installing this thing will agree that this is not the way to go. Of all the API Managers out there (we've tried 4), WSO2 is the only one were you need to know how this dragon of a java application works internally. Did I already mention the humongous amount of config files?

Verified User
Team Lead in Information Technology
Consumer Services Company, 501-1000 employeesPros
NGINX
- 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)!
Senior Software Engineer
RocketripComputer Software, 11-50 employees
WSO2 API Manager
- Nice API store-front capability
- Management of users and permissions

Verified User
Project Manager in Information Technology
Higher Education Company, 10,001+ employeesCons
NGINX
- 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.
Senior DevOps Engineer
Conversant Inc. (formerly Dotomi)Marketing and Advertising, 5001-10,000 employees
WSO2 API Manager
- Installation of this product is a hell. You need to be an expert to get this running together with WSO2 Analytics. It uses a really confusing method of "port + 1" to connect extra products. I guess this was meant to provide a handy way to add new WSO2 products. In reality you'll need to scroll through numerous config files to set this straight. If you use this out of the box, everything will work all right. But the moment you add SSL certificates, DNS names and you'll need special ports to configure your firewall, this product becomes unmaintainable.
- The "Store" provides a nice way to group API's. However, the "Publisher" does not... if you have more than 30 API's searching for API's becomes really annoying.
- The number of configs in this product is huge. As a developer myself, I've never seen (and definitely never created) a product that needed that much config files. Installation and maintenance of products should be stupidly simple, since no developer nor infrastructure person wants to learn something that "just" needs to be a tool.. opposed to being a whole new area of expertise. After using WSO2 API Manager for a while, we wanted to change the admin password... this should be simple enough, like just change the password in "Carbon." But nope. The whole WSO2 environment crashed. We just gave up. Too dangerous.
- Why so many different "products"? Publisher, Store, Carbon, and numerous hidden interfaces. Analytics, ESB whatever... No wonder there are so many config files and port issues. Make it simple!!!

Verified User
Team Lead in Information Technology
Consumer Services Company, 501-1000 employeesPricing Details
NGINX
General
Free Trial
Yes
Free/Freemium Version
Yes
Premium Consulting/Integration Services
Yes
Entry-level set up fee?
Optional
Starting Price
—WSO2 API Manager
General
Free Trial
—Free/Freemium Version
Yes
Premium Consulting/Integration Services
Yes
Entry-level set up fee?
No
Starting Price
—Usability
NGINX
NGINX 9.0
Based on 1 answer
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.

Verified User
Engineer in Information Technology
Information Technology and Services Company, 10,001+ employeesWSO2 API Manager
No score
No answers yet
No answers on this topic
Support Rating
NGINX
NGINX 8.1
Based on 8 answers
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. 


Principal, Lead developer, Lead designer
PelagoInternet, 1-10 employees
WSO2 API Manager
No score
No answers yet
No answers on this topic
Alternatives Considered
NGINX
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
Senior Software Architect
Beneath The InkComputer Software, 1-10 employees
WSO2 API Manager
IBM API Manager is a better enterprise wide tool.

Verified User
Project Manager in Information Technology
Higher Education Company, 10,001+ employeesReturn on Investment
NGINX
- 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.
Head of Development Technologies
Top Floor TechnologiesInternet, 11-50 employees
WSO2 API Manager
- We've moved away from legacy SOAP services where nobody knew what services was used by who. WSO2 eliminated at least 90% of time spend on any service.
- Creating API's (or actually creating the API Management layer...) is so simple that new developers can get away with it in no time. Again, real time gainer.
- Since creating API's is so simple, developers are very fast in adopting a kind of "Domain thinking". In comparison with Azure API Manager: Azure does not demand knowledge of "how" the product works, but it's definitely more difficult to get an API up and running in Azure. And for some reason, azure does not promote clean domain driven architecture. Domain Driven architecture is the greatest time saver strategy possible. And WSO2 fits nicely in there.

Verified User
Team Lead in Information Technology
Consumer Services Company, 501-1000 employees