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 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.

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.

I use Amazon API Gateway for student data management of microservices to share between other systems. The solution is used between different applications in our organization. Amazon API Gateway is used along with Salesforce, Oracle, ServiceNow and SQL solutions. 

The simplicity of use is one of the vital features of Amazon API Gateway. It's a low-code solution that helps our company manage operations seamlessly. 

We have all the calls to our servers through API Gateway. We use API Gateway at the front, and everything else is hidden behind the firewall. API Gateway routes calls to our servers. We use API Gateway for our calling solutions.

API Gateway is out of the box and works well with Amazon products. It handles security and other headaches, keeping our database and servers secure. Moreover, it's easy to integrate with Amazon products.

My use case for Amazon API Gateway involves using it for backend APIs and mostly private API Gateways. We utilize it within the context of a microservices architecture. The front-end technology connects through the API Gateway to backend services running on Lambda, making the API Gateway an endpoint for reaching backend services.

Amazon API Gateway provides easy scalability and fast deployment, making it less time-consuming to spin up services. Its serverless technology allows our applications to scale seamlessly according to demand.

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.