Amazon API Gateway vs. NGINX Plus

Experienced a lack of available programming languages while working on a minor project. I had to halt the project and wait for it to be added later. It took ages and had a hit on our productivity. It has a centralized management system which helps and an easy interface which helps to manage multiple tasks in case of large-scale operations and projects.

Incentivized

Makes our life easy as application admins in securing our applications and making them accessible. We can easily add an application within a few minutes and define the backend servers right away.

Incentivized

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

Incentivized

• APIGW
• Policy Enforcement
• Centrally Manage API Traffic

Incentivized

• Client certificates are troublesome when trying to attach them to API GW stages.
• Debugging across several services can be difficult when API GW is integrated with Route 53 and another service like Lambda or EC2/ELB.
• Creating internal/private APIs, particularly with custom domains, can be unintuitive.

Incentivized

• An AI bot would be cool to help build config files
• More webinars for advanced NGINX Plus would be great
• GUI tool... might already be one available

Incentivized

No reason not to renew it, we are happy with it.

Incentivized

Very easy to use

Incentivized

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.

Incentivized

We had an issue after upgrading from RHEL 7 to 8, and there were some issues that the security team imposed upon the platform with a scanning tool. We also had a VXLAN environment that was not properly sending a gratuitous arp to the network. NGINX support was instrumental to speedily resolving our issue.

Incentivized

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.

Incentivized

The API and dashboard alone make NGINX Plus a better choice.

Incentivized

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

Incentivized

• We are planning by using NGINX it can greatly reduce our OPEX by 50% "just our own running APIGW" the cascading effects in the long run will be much more.

Incentivized