Amazon API Gateway vs. SwaggerHub

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

ReadyAPI and SwaggerHub are a match made in heaven. Being able to so easily import the API directly into ReadyAPI and then being able to generate a test suite from the API is my favorite part of these softwares. We have rather large services so building out the API can take some time

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

• Treating the design as documentation ensures that we have consistent and well defined APIs
• API consumers can export the swagger definition or code stubs to use within their development environment
• We can iterate through multiple versions of a definition privately before making a version publicly available

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

• The user interface could be more improved to sustain with other similar tools in the market.
• Beneficial if we have better integration with third party softwares.
• Nice to have ability to download the documentation in usable formats.

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

The only other product we looked at was Postman. But we liked the SwaggerHub UI & the integrations it has with the AWS API gateway. Though Postman has some other great features like the ability to write test cases & execute them, SwaggerUI was more convenient to document & share them.

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

• Faster API development lifecycle.
• Reduced discussion time when building a new vital API endpoint.
• Complete documentation which makes the new team member onboarding process easier.

Incentivized