Amazon API Gateway vs. Stoplight

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

API mocking, testing, and sharing are all built in functions for StopLight that work quite well. They even have functionality for generating OAI and RAML code as well, which is a huge plus. AS for as areas where StopLight is not appropriate, if you're doing anything other than API testing, StopLight may not be appropriate for use.

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

• OpenAPI support
• Markdown supports
• Git integration

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

• Simplicity of set up. Although it's not difficult, there are tools out there that are easier to set up for testing endpoints.
• Again, it's perfectly functional, but some competitors I think have a more user friendly UI to them.

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

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

I'd like to also throw Runscope and Fiddler into the mix. Between StopLight and all these competitors, we've chosen StopLight primarily for the support, ease of use, and reliability. Most tools out there today are top-notch, so it really comes down to personal preference and different use-cases. Having used other API testing frameworks, StopLight definitely stacks up against the competition.

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

• Increased efficiency
• Improved comminication between backeend and frontend

Incentivized