serverless-application-model
Our great sponsors
serverless-application-model | aws-lambda-runtime-interface-emulator | |
---|---|---|
98 | 4 | |
9,231 | 865 | |
0.3% | 1.0% | |
8.9 | 5.2 | |
11 days ago | 9 days ago | |
Python | Go | |
Apache License 2.0 | Apache License 2.0 |
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.
serverless-application-model
-
Simple and Cost-Effective Testing Using Functions
The complete solution with SAM is available here.
-
Deploying a Serverless Dash App with AWS SAM and Lambda
There are many options to deploy Serverless Applications in AWS and one of them is SAM, the Serverless Application Model. I chose to use it here, because it doesn't add too many layers of abstraction between what's being deployed and the code we write and our infrastructure is quite simple.
-
Serverless Apache Zeppelin on AWS
The solution uses AWS SAM with the global configuration for Lambda functions and the public API you can use to access Apache Zeppelin. The stack deployment provides the URL as an output value.
-
Using design patterns in AWS Lambda
When you combine this with the AWS Serverless Application Model you can also very easily include your dependencies. Or use a compiled language like golang for your Lambda functions. You simply run sam build before you run the aws cloudformation package and aws cloudformation deploy commands. SAM will build the binary and update the template to point to the newly built binary. Package will then upload it to S3 and replace the local reference to the S3 location. Deploy can then create or update the stack or you can use the CloudFormation integration in CodePipeline.
-
Serverless Site Health Check Notification System
I'm a big fan of using an Infrastructure as Code (IaC) approach for any project. My go to tools for this are the Servlerless Application Model (SAM) and it's associated CLI (SAM CLI). For more official use cases and for cross platform apps I typically use Terraform.
-
Starting My AWS Certification Journey as a Certified Cloud Practitioner
AWS SAM
-
API Gateway, Lambda, DynamoDB and Rust
Kicking off the tour and not starting a war, but I'm going to be using the Serverless Application Model.
-
Consuming an SQS Event with Lambda and Rust
The diagram here is super simple. I'm going to write something a little later that shows how this code could fit into a bigger workflow, but for now, I'm keeping it basic. And yes, that's the SAM Squirrel in there.
-
AWS Data Engineer Associate Certification - Coming Soon
Interestingly, AWS CDK and SAM are both explicitly mentioned. While CDK broadly addresses Infrastructure as Code, SAM is highlighted for its role in developing serverless data pipelines - a hugely underrated concept.
-
A Beginner's Guide to the Serverless Application Model (SAM)
Naturally, there are several options available to declare your cloud resources. The options with the most popularity are the CDK, AWS CloudFormation, SST, Serverless framework, Terraform, and AWS SAM. There are others, but when talking about Infrastructure as Code (IaC), these are the ones you hear about most often.
aws-lambda-runtime-interface-emulator
-
Understanding the AWS Lambda Runtime API
Enter the aws-lambda-runtime-interface-emulator. This tool will allow us to emulate the AWS Lambda Runtime API locally (I suspect that the AWS SAM uses this tool under the hood as well). The aws-lambda-runtime-interface-emulator is designed to be used with Docker. Still, nothing stops us from containerizing our code for the sake of development and then, whenever we are ready, proceeding with deployment how we wish to. This local workflow is a bit more involved than the previous one, but it might be a valid alternative for those not using AWS SAM or are already using containers to deploy their Lambdas.
-
Puppeteer performance in AWS Lambda Docker containers
There is a special tool to test AWS Lambda images locally. It's called AWS Lambda Runtime Interface Emulator (RIE). You have two options: include RIE in your image or install it locally. We don't need it in the production image, so let's choose the second option. We will download binary locally and mount it to our image if we need to test it.
-
Ask HN: Does anyone else find the AWS Lambda developer experience poor?
Suggestions:
1. If you are building APIs and using Lambda functions as targets from an API Gateway API, look into libraries like serverless-wsgi (Python) or wai-handler-hal (Haskell) that translate between API Gateway request/response payloads and some kind of ecosystem-native representation. Then as long as you're writing code where all state gets persisted outside of the request/response cycle, you can develop locally as if you were writing for a more normal deploy environment.
2. Look into the lambda runtime interface emulator ( https://github.com/aws/aws-lambda-runtime-interface-emulator... ). This lets you send invoke requests to a fake listener and locally test the lambda more easily. While the emulator is provided in the AWS container base images, you don't need to run it inside a container if you're deploying with zip files. (AWS-provided container images automatically enable the emulator if not running in a lambda runtime environment, and using docker for port remapping is nice. But not at all required.)
3. Get really good at capturing all requests to external services, and mocking them out for local testing. Whether this is with free monads, effect systems, gateway classes will depend on your language and library choices.
What are some alternatives?
aws-elastic-beanstalk-cli - The EB CLI is a command line interface for Elastic Beanstalk that provides interactive commands that simplify creating, updating and monitoring environments from a local repository.
Moto - A library that allows you to easily mock out tests based on AWS infrastructure.
LocalStack - 💻 A fully functional local AWS cloud stack. Develop and test your cloud & Serverless apps offline
serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project
docker-lambda - Docker images and test runners that replicate the live AWS Lambda environment
sst-start-demo - A simple SST app to demo the new `sst start` command
aws-lambda-go - Libraries, samples and tools to help Go developers develop AWS Lambda functions.
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.
chrome-aws-lambda - Chromium Binary for AWS Lambda and Google Cloud Functions
aws-sam-cli - CLI tool to build, test, debug, and deploy Serverless applications using AWS SAM
aws-lambda-python-runtime-interface-client