Amazon API Gateway Information Reviews & Insights

Our organization uses Amazon API Gateway to orchestrate and consolidate web service APIs across projects. It is a useful multi-purpose tool, and we use it to integrate authentication to our APIs, build out consolidated responses from different API endpoints, and to provide a single point of access to multiple web service APIs developed using a myriad of different technologies and programming languages. It also provides a great way to document and integrate web services via Swagger integrations.

If you are using AWS as your primary infrastructure provider, [Amazon] API Gateway is the best gateway option for you to integrate and expose web service applications. It integrates well with security controls provided by AWS such as VPC limits and security groups. Furthermore, it is very easy to use Amazon API Gateway to provide an out-of-the-box auth solution by integrating AWS Cognito. We were able to get authentication and authorization integrated very quickly in to a large number of APIs under the same product umbrella by utilizing API Gateway's integration with Cognito.
[Amazon] API Gateway is not the best solution if you're trying to build a microservices architecture, as it's service registration methodology is still quite clunky. For microservices, you'd be better off utilizing tools built specifically for that purpose.

Apigee Edge and SwaggerHub

Our primary architecture is AWS, so we selected [Amazon] API Gateway as our gateway solution. While ApiGee and SwaggerHub provide great solutions for service orchestration, [Amazon] API Gateway provided the best integrations with our web services which were mostly running within AWS behind AWS load balancers. [Amazon] API Gateway could also act as a trigger for a set of AWS Lambda functions that we were using for small task APIs.

Amazon API Gateway is one of the best way to host your services under the AWS umbrella and easy to provide scalability and reliability. Our company is exposing an API service to various clients with custom billing and limitation. In this task, Amazon API provides a great infrastructure and security to host REST APIs with HIPAA compliances.

Amazon API Gateway is a very powerful tool, for a small organization. Good for quick developing microservices . It is also great when used as a API gateway that provides authentication over microservices.

Tyk, Apigee Edge and Azure API Management

As AWS API comes with more security and API key authentication functions, it's easy for the organization to handle the various customers based with different level of permission. And also very easy comparable to others for tracking the API calls. Also, scalability and reliability are major points to consider for AWS API gateway.

I have been using API Gateway along with other AWS products. API Gateway provides smooth API architecture which you can easily deploy. In my company, we're using API Gateway integrated with AWS Lambda. API Gateway has mapping templates which you can use to create an event-based architecture. It also gives you the opportunity to protect your endpoints, whether your own "authorization lambda," or via X-API-Key provided from AWS. You may decide to not use an API Key. It gives you the opportunity to define HTTP request headers, query string parameters, or even define the request and response body. You can also export your API as a Postman collection or Swagger to publish it to your users. In our company, we have six different API Gateway instances working with tens of Lambdas. Each instance has a different environment, which provides you with a unique link. We are very happy with API Gateway and do not face any issues except timeout limits until now. Also, enabling CORS is pretty easy, and API Gateway provides you all of the security which makes you feel more comfortable and focus on your work.

I think if your software is suitable for event-based architecture, and if you can use Lambda in your architecture, API Gateway is a must and complementary product to use. It provides you tools that you can use to build very scalable and secured endpoints. In my company, we have divided our software into domains and created API Gateway instances for each domain connected to our AWS Lambdas. This provided us better and well-organized APIs which we provide to our customers. The feedback we've received from customers is very positive, and they think that our APIs are well designed and look professional.

Since we have been using AWS products since the beginning, we did not think about using any competitors of API Gateway. It has great and strong integration with other AWS products.

At our firm, we provide different services and at different levels to our clients. With using Amazon API Gateway, it became possible for us to expose our services through simple REST endpoints. We have it synced up with different Amazon Lambda functions that handle the bulk of the processing and then exposing them via the API gateway.

Amazon AWS services, including the API Gateway, have an excellent reputation in the development community. They have one of the best up-times for any comparable cloud hosting service. The fact that the service scales up as the load requirements increase, and that clients are only charged based on these usage metrics, makes it a winner for us.

Amazon CloudWatch and Amazon Elastic MapReduce