fl-aws
docker-lambda
fl-aws | docker-lambda | |
---|---|---|
1 | 8 | |
15 | 5,852 | |
- | - | |
0.0 | 0.0 | |
over 7 years ago | over 1 year ago | |
C# | ||
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fl-aws
-
Ask HN: Does anyone else find the AWS Lambda developer experience poor?
Living in my team's bubble i thought everyone runs or tries to run parallel environments: prod, staging, dev, but also an individual (person) or feature env. Why? Because there's no emulator or documentation that will teach you real behavior. Like others have said, AWS seems out of this world. Just like GCP and Azure i might add. Some things you don't expect and they mesmerize you how smart they are. Some you expect and you can't fathom how come you're the "only" one screaming. Random thought: this is how i ended up logging all I bumped into into "Fl-aws" https://github.com/andreineculau/fl-aws
Back to the point: reality is that many build their AWS environment (prod) manually, maybe they duplicate once (dev) also manually, maybe they use some automation for their "code" (lambda) but that's it. This implies it's practically impossible to run end-to-end tests. You can't do that in prod for obvious reasons and you can't do it in dev either - you have many devs queueing, maybe dev is not in sync with prod etc.
My team ran cloudformation end-to-end. We actually orchestrated and wrapped cloudformation (this is yet another topic for not using terraform etc) so that if smth couldn't be done in CFN, it would still be automated and reproducible. Long story short, in 30 minutes (it was this long because we had to wait for cloudfront etc) we had a new environment, ready to play with. A total sandbox. Every dev had their own and it was easy to deploy from a release artifact or a git branch to this environment. Similarly you could create a separate env for more elaborate changes to the architecture. And test in a live environment.
Finally to your question: how do you test end-to-end?
If we talk about lambdas because that's where the business logic lies in a "serverless" architecture, then the answer is by calling the system which will eventually call your lambda/s along the way. If your lambda ia sitting behind AWS gateway, then fire an http request. Is it triggered when objects land on S3? Then push some object to S3. How do you assert? Just the same - http response, S3 changes etc. Not to mention you can also check cloudwatch for specific log entries (though they are not instant).
With this type of a setup, which sounds complex, but it is not since it is 100% reproducible (also from project to project - I had several), adding this proxy-to-my-dev-machine lambda would mean I can make local changes and then fire unit AND end-to-end tests without any changes pushed to AWS, which is the main time/energy consumer imo.
PS: sorry for the wall of text. Like i said i recently realized that the development realities have huge discrepancies, so i tried to summarize my reality :)
docker-lambda
-
There is framework for everything.
https://github.com/dherault/serverless-offline https://github.com/lambci/docker-lambda
-
Bitbucket Pipeline build and deploy Lambda Container Image in AWS
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
-
How to publish and use AWS Lambda Layers with the Serverless Framework
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:
-
AWS linux container image
I end up using Lambda a lot so lambci is very useful for local testing: https://github.com/lambci/docker-lambda
-
Should Lambda services be built in the cloud (vs. local environment)?
There are kind souls in this world who created this: https://github.com/lambci/docker-lambda
-
Ask HN: Does anyone else find the AWS Lambda developer experience poor?
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
-
How To Test AWS Lambda: Everything You Need To Get Started.
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.
-
How To Debug AWS Lambda: A Detailed Overview
Want to emulate AWS environments? Try docker-lambda.
What are some alternatives?
aws-lambda-runtime-interface-emulator
serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project
sst - Build modern full-stack applications on AWS
bref - Serverless PHP on AWS Lambda
supertest - 🕷 Super-agent driven library for testing node.js HTTP servers using a fluent API. Maintained for @forwardemail, @ladjs, @spamscanner, @breejs, @cabinjs, and @lassjs.
Moto - A library that allows you to easily mock out tests based on AWS infrastructure.
examples - Serverless Examples – A collection of boilerplates and examples of serverless architectures built with the Serverless Framework on AWS Lambda, Microsoft Azure, Google Cloud Functions, and more.
faasd - A lightweight & portable faas engine
aws-embedded-metrics-node - Amazon CloudWatch Embedded Metric Format Client Library
aws-cli - Universal Command Line Interface for Amazon Web Services
WeasyPrint - The awesome document factory