Amazon API Gateway

Amazon API Gateway vs Apigee. How do they compare as an API Gateway? What is the equivalent functionality, similarities, and differences moving from Apigee API GW to AWS API GW?

I use AWS Lambda because it is the most mature of the major cloud platforms for serverless functions. The fact that you can add VPC configs at the start is huge from a security perspective. However, it does take a lot of work to configure the Amazon VPC to work with AWS Secrets Manager and Lambda. It's also nice because it works so well with Amazon API Gateway

I typically use it to connect with databases to insert and extract information for downstream analytics.

I won't be surprised if one day the majority of workloads run on this service. Not having to manage and maintain infrastructure is truly a blessing.

Excellent API Gateway, some quirks but most are being addressed over time, easy integration with Lambda Amazon API Gateway

Triggers the Lambda function from a GitHub WebHook push into https://github.com/smyleeface/smylee_hugo_site. Amazon API Gateway

It provides me with POST endpoints; I don't run servers and some third-party services need to POST data to my application. Amazon API Gateway

API Gateway in conjunction with Lambda has allowed us to become 'serverless'. We have a number of API endpoints that range from simple CRUD operations, through to triggering chains of complex background jobs. Like Lambda, this service has released us from getting bogged down in infrastructure management, freeing up huge amounts of time to focus on solving business problems. Amazon API Gateway