In our organization, Amazon API Gateway helps developers to manage, create, publish, maintain, monitor, and secure APIs of any and all scales. It helps a lot in streamlining administrations. It has a fantastic setup and security for hosting REST APIs that comply with HIPPA guidelines and regulations. Its operation is very easy to use and flexible.
Pros
Hosting REST APIs that follow HIPPA guidelines and regulations.
It provides mock responses that help keep check of the automation scenario and reality.
It is easy to use and can be customized as per requirements.
Cons
The service and support are mediocre at best.
It is very hard to debug when something in the code is incorrect..
Various programming languages are missing.
Likelihood to Recommend
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.
We use Amazon API Gateway in conjunction with AWS Lambda functions and the Serverless framework to rapidly build microservices. This combination is very powerful, particularly for small development teams, because it allows us to delegate work to AWS; we can focus our development effort only on features that yield competitive advantages for our business.
Pros
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.
Cons
API Gateway introduces some concepts, such as Stages and Integration Requests, that are foreign to most developers. The documentation hints in the Console help, but sometimes these concepts are not transferred to frameworks like Serverless.
Systems that use API Gateway may behave differently in end-to-end tests in local or CI environments.
Navigating the Console can be confusing.
It could be easier to codify API Gateway configurations.
Likelihood to Recommend
Amazon API Gateway is a very powerful tool, particularly for small engineering teams. It is ideal for rapidly developing microservices when used in conjunction with the Serverless framework and AWS Lambda. It is also great when used as a conventional API gateway that provides authentication and routing over microservices. It would not be useful for exposing a monolithic application.
