aws-sam-cli

There are DynamoDB Local[1] and AWS SAM CLI[2], both from AWS, which allow you to self-host DynamoDB and AWS Lambda functions. ;) That said, I agree with your argument, but found it rather funny that you just picked two AWS services you can indeed run locally. [1]: https://docs.aws.amazon.com/amazondynamodb/latest/developerg... [2]: https://github.com/awslabs/aws-sam-cli/

I mean this: https://github.com/awslabs/aws-sam-cli

At my company we have a few small basic API's now running on Lambda and API Gateway. We're a big AWS shop and I can't envision us ever moving to Google or Azure, so vendor lock-in isn't much of a concern. At first local development was a bit challenging, but frameworks like Serverless help with that. Also, many don't know this, but you can run and debug AWS Lambda locally with AWS' own tooling. Using this to build out and test Lambda's before creating them with Terraform has been priceless: https://github.com/awslabs/aws-sam-cli

You can run and debug AWS Lambda locally. We've done it with several of our API's: https://github.com/awslabs/aws-sam-cli

I use SAM CLI so I can run my code locally in a realistic environment. So you can skip the build/zip/upload/deploy process. https://github.com/awslabs/aws-sam-cli

You can replicate some of the live-like environment using SAM[1] and SAM-local[2]. Combined with services like ngrok[3] you can even test remote hooks and such. [1] https://github.com/awslabs/serverless-application-model [2] https://github.com/awslabs/aws-sam-cli [3] https://ngrok.com/ or http://serveo.net/

I were using SAM for month or two and then switched back to CloudFormation, because I felt limited (not all features of API Gateway were implemented, duplicated stages, problems with instrict functions). However, I watch their GitHub repository for changes and I noticed many missing features are implemented on AWS re:invent basis (duration between next conference). The worth-noting feature of SAM is definetely aws-sam-cli (former: aws-sam-local) [1], which is a tool for developers to parse SAM template and invoke Lambda function in the docker on local machine. It was great to test simple APIs (start-api mode), but when some API started using custom authorizers or response was a compressed payload of png image it was not very helpful. Personally, I am working on a fork of aws-sam-cli to implement it to work with CloudFormation. [1]: https:

I'm using this, and so far it's working just fine: https://github.com/awslabs/aws-sam-local I'm only testing Lambda functions with it, and not really testing APIG + Lambda integrations or anything fancier. I prep the local db, mock a Lambda event, write the mocked event to a JSON file, then use command line options to run the event against AWS SAM local, then get the response and compare it to the expected response.