gateway VS docker-lambda

We had great success with https://github.com/apex/gateway

I write Lambda functions in golang. In dev I run the function as local http server. In prod I map a custom domain to the lambda, routing is done internally to the function. API Gateway is only used for the top level route. This workflow is enabled by https://github.com/apex/gateway

In principle I try to avoid Amazon Web Services that lock me into the platform. So, for my dev stack I run a few other containers to give me the equivalent of the prod environment, RDS (MySQL or PostgreSQL), ES (OpenDistro), S3 (Minio), and SES

https://github.com/dherault/serverless-offline https://github.com/lambci/docker-lambda

Step 2: Push a container from your local machine to ECR. Currently, I use sample python lambda docker from https://github.com/lambci/docker-lambda.git

You can see the following projects for some examples of using this plugin to build a layer. They all leverage Docker and the docker-lambda images to compile for AWS’s Lambda environment on any operating system:

I end up using Lambda a lot so lambci is very useful for local testing: https://github.com/lambci/docker-lambda

There are kind souls in this world who created this: https://github.com/lambci/docker-lambda

If all you need is the ability to run a lambda function's code locally you might interested in docker-lambda[1]. I haven't really used localstack or SAM but a couple of years ago when we needed to run some lambda functions locally for development docker-lambda worked well enough.

[1] https://github.com/lambci/docker-lambda

Docker Lambda — Docker Lambda is a tool which tries to replicate the AWS Lambda environment as closely as possible, but within a Docker container. Docker Lambda has support for most of the AWS Lambda run times.

Want to emulate AWS environments? Try docker-lambda.