What users are saying about
Top Rated
73 Ratings
43 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.2 out of 100
Top Rated
73 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.9 out of 100

Likelihood to Recommend

Amazon API Gateway

API GW is great for giving access to asynchronous operations that are fast and don't need to be online all the time. Lambda functions are the classic example. In the past, an operation that is called on via an HTTP endpoint would be implemented using a server-based solution. With high availability in place that would include a server or two and a load balancer. Over time this setup can be costly, especially if the service is not used at full capacity; cycles are wasted when the servers are sitting there waiting to respond.If the operation can be distilled down to a function, an API GW + Lambda solution could be put in place that performs the operation as needed only when requested. Comparing the low price point for API GW requests and Lambda CPU+Memory, the savings can be night and day over the server-based implementation.
Michael Jenkins | TrustRadius Reviewer

NGINX

Nginx is well suited for serving any static content - whether that be images, JS files, HTML files, CSS files, videos, etc. If you have a high-traffic website, Nginx will be a great fit because it handles large number of requests extremely efficiently. Nginx has full support on Unix systems, but only has limited support on Microsoft Windows machines.
Gabriel Samaroo | TrustRadius Reviewer

Feature Rating Comparison

API Management

Amazon API Gateway
8.5
NGINX
API access control
Amazon API Gateway
9.1
NGINX
Rate limits and usage policies
Amazon API Gateway
9.1
NGINX
API usage data
Amazon API Gateway
8.7
NGINX
API user onboarding
Amazon API Gateway
6.7
NGINX
API versioning
Amazon API Gateway
9.0
NGINX
Usage billing and payments
Amazon API Gateway
8.8
NGINX
API monitoring and logging
Amazon API Gateway
8.0
NGINX

Pros

Amazon API Gateway

  • API Gateway integrates well with AWS Lambda. This allows us to build a web server in the language and framework of our choice, deploy it as a Lambda function, and expose it through API Gateway.
  • API Gateway manages API keys. Building rate limiting and request quota features are not trivial (or interesting).
  • API Gateway's pricing can be very attractive for services that are accessed infrequently.
Anonymous | TrustRadius Reviewer

NGINX

  • Straight-forward configuration format that users of all skill levels can learn, and yet is powerful enough for the huge breadth of features that Nginx provides.
  • Massive scale right out the box. We've never had a Nginx instance overwhelmed by requests, and if we did it would be trivial to spin up more Nginx instances to handle the load.
  • SSL termination means that we can deliver content over HTTPS without needing our individual services to require TLS support. This saves us a lot of time and headache while keeping us secure.
  • Nginx is open-source and free, meaning that anyone can use it to power their services, from individual projects to billion-dollar websites.
Tyler Johnson | TrustRadius Reviewer

Cons

Amazon API Gateway

  • I think there should be another way of enabling CORS. It basically creates OPTIONS for every endpoint, which makes your API Gateway look complicated.
  • The integration timeout limit is 30 seconds, which limits you into that time.
  • API Gateway UI should be improved and should work correctly when more than two people are adding/editing endpoints.
Anonymous | TrustRadius Reviewer

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.
L Matthew Blancett | TrustRadius Reviewer

Usability

Amazon API Gateway

No score
No answers yet
No answers on this topic

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.
Anonymous | TrustRadius Reviewer

Support Rating

Amazon API Gateway

Amazon API Gateway 10.0
Based on 2 answers
We always had a great experience with the AWS support team. They were always on time and very dependable. It was a good partnership while we worked to resolve our issues.
Anonymous | TrustRadius Reviewer

NGINX

NGINX 7.8
Based on 10 answers
I'm explicitly rating the open-source version of NGINX here. The open-source version has good documentation and useful examples. As one of the most web servers in the world, there is a wide range of tutorials and examples to learn from. This does have the drawback of potentially using older documentation, but NGINX has excellent default behavior, and the official documentation is easy to use. Their paid support seems excellent as well, though we haven't taken advantage of it yet.
Anonymous | TrustRadius Reviewer

Alternatives Considered

Amazon API Gateway

When we tested Azure API Management at the time, it had serious connectivity issues, it was very unstable, and it needed to do a lot using the command line. Comparing with the AWS solution, which was more mature, and the fact that we have services in use on AWS, we ended up choosing to continue using AWS products. This so as not to run the risk of increasing latency in accesses, and of some functionality not working, due to being developed yet.
Anonymous | TrustRadius Reviewer

NGINX

Nginx struck the right balance for us of raw speed, power, convenience, and simplicity.
  • I don't like the idea of hosting all of our open source PHP-based websites on Microsoft Windows servers with IIS, so that option was out first.
  • Next, we had experience with Apache already, and were initially considering sticking with that, however it was decided that it would take too much administration time to properly configure and tune the server, especially considering it would need to occur on an ongoing basis.
  • I've personally had experience with Litespeed Web Server, but we wanted something a little bit lower level--we don't need to actually manage our virtual hosts within an admin UI, and we wanted to stick with open source as much as possible. One huge benefit of Litespeed, however, is that it's .htaccess-compatible, meaning it's a much smaller transition from Apache in some cases.
  • LightTPD was the closest contender to Nginx when all was said and done. We chose Nginx because some of us were more familiar with it or had some experience with it, and Nginx seemed to have more documentation and resources online for finding assistance at the time.
Ben McClure | TrustRadius Reviewer

Return on Investment

Amazon API Gateway

  • ROI is negative, you need either to hire them to work with you or spend days/weeks to figure out issues.
  • For some of the projects in the end it is not worth it, it is just a "buzz" to use serverless but not practical.
  • Service is easy to set up authorization and it is easy to manage.
Anonymous | TrustRadius Reviewer

NGINX

  • Improved the reliability of our site. Before using Nginx, with Apache as our app server, there were times when we had to manually go in and restart Apache to bring the site back online. We've never had to do that with Nginx.
  • Made our web server more memory efficient -- Nginx has a very small memory footprint, on the order of under 100 MB. This makes it suitable even for cheap VPS machines.
  • The Nginx community provides online examples of configurations, so it saves us time in writing the config files from scratch.
Anand Chhatpar | TrustRadius Reviewer

Screenshots

Pricing Details

Amazon API Gateway

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Amazon API Gateway Editions & Modules

Edition
First 300 Million$1.001
Past 300 Million$0.901
  1. Per Million
Additional Pricing Details

NGINX

General

Free Trial
Yes
Free/Freemium Version
Yes
Premium Consulting/Integration Services
Yes
Entry-level set up fee?
Optional

NGINX Editions & Modules

Edition
NGINX PlusContact sales team1
NGINX ControllerContact sales team
NGINX App ProtectContact sales team
NGINX AmplifyContact sales team
  1. per instance/enterprise pricing available
Additional Pricing Details

Rating Summary

Likelihood to Recommend

Amazon API Gateway
8.1
NGINX
8.8

Usability

Amazon API Gateway
NGINX
9.0

Support Rating

Amazon API Gateway
10.0
NGINX
7.8

Add comparison