Amazon API Gateway Reviews

We are using API Gateway to route the traffic to our Lambdas. Every API pass is linked to some of the Lambdas. When traffic hits CloudFront, it redirects it to API Gateway, which then redirects it to the respective Lambda server. We have different kinds of services invoked through these Lambdas.

When we shifted to the serverless model, many responsibilities, such as patching the servers and taking care of backups, are managed by AWS. This reduces our overhead.

We primarily use it for real-time use cases where we have used Lambda with the API Gateway. So, the backend is a Lambda server. We are implementing a serverless architecture with the API Gateway. 

We've implemented risk score models within the Lambda. Thus, whenever someone requires a risk assessment for a prospect in need of a loan, they access our Amazon API Gateway. In the backend, it triggers the Lambda service.

So, within the Lambda, our ML model predicts whether the customer falls into the high-risk or low-risk category. Then, it sends a response to our frontend application, which is an Android-based application.

Currently, our use cases are relatively simple. Even though we host ten different models, the use cases are similar. We have configured the API gateway for various URLs and receive hits from different services like tractors, two-wheelers, and mobiles. 

The most valuable aspects are its user-friendliness and simplicity. These two features make it easy to work with. 

Additionally, it's cost-effective, even as our workload and the number of APIs we manage have increased. 

The integration with other API services, such as Lambda, EC2, and Kubernetes, is also incredibly useful.

We mainly use these APIs for east-to-west communication within our internal system and partner collaboration. While most companies prefer tool-based API management for partner collaboration, for internal consumption, and integration between application insight, we tend to use cloud-native tools provided by AWS.

The most valuable features are the standard ones that APIs offer. Depending on the requirements, Azure API management's throttling feature is used for continuous consumption. Otherwise, we rely on the default features available. 

Since it is mainly for internal communication, we haven't received any concerns or requests for better tools or additional features. The initial tools provided by Amazon API Gateway suffice for our needs.

All of my APIs and microservices are behind the Amazon API Gateway. When someone sends a request to the API Gateway, it performs validation and then forwards it to the appropriate microservice. Several microservices, such as payment services, deposit services, and account services, are all behind the API Gateway.

For me, there are many valuable features. The solution is a managed service and requires minimal configuration, which makes it easy to launch an API. Moreover, there is support for analytics and configuration options for volume, security, rate limits, and more.

We use Amazon API Gateway to expose some APIs. I worked for three companies that mostly used API Gateway for exposed services and complex use cases like expose headers. The solution is used to personalize responses, provide more simulations, and facilitate communication between the services. The solution is also used to direct some requests to Lambda and ECS.

Amazon API Gateway can integrate with ECS and Lambda. With Amazon API Gateway, you can have massive integrations that are quickly integrated.

We are using API Gateway for exposing our APIs to external organizations. We use it to secure our APIs and as a jump server type, so that all the APIs are exposed or published from one particular source, which is the API Gateway.

From my perspective of ease of use, it is very good. API Gateway is very simple since it's just clicks and we get it. We have a pay-as-you-go model. The payment is a little bit on the costlier side when I look at the amount we have to pay. It is good but costly. I think authorization should not have any issues.

We primarily use the solution as an API gateway. The APIs are managed by serverless applications. It's an API gateway from Layer 7.

The integration with Comdata is very good.

The product is affordable.

It is easy to set up. It is also quick to deploy.

The solution is reliable. It is very stable. 

The solution can scale well. 

Our primary use case involves working on the cloud side, specifically using AWS serverless components, CI/CD pipelines, data storage with S3 buckets, and databases like MySQL, DynamoDB, and DocDB. Additionally, we use API Gateway for REST API development, SageMaker for machine learning model training, and more.

My experience shows that API Gateway provides a secure endpoint for customers using OAuth 2, integrates seamlessly, and enhances customer access to services and product information.