serverless-application-model
LocalStack
Our great sponsors
serverless-application-model | LocalStack | |
---|---|---|
98 | 154 | |
9,231 | 52,055 | |
0.3% | 1.0% | |
8.9 | 9.9 | |
9 days ago | about 4 hours ago | |
Python | Python | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
LocalStack
- LocalStack – a functional local AWS cloud stack
-
Let's build a screenshot API
Later you can use any S3 compatible storage because the code I write will still work, but for testing purposes on my local machine, I will use LocalStack:
-
LocalStack e AWS CLI: Como desenvolver localmente com a AWS
Acesse o site da LocalStack e faça login.
-
Cutting down AWS cost by $150k per year simply by shutting things off
To give this a slightly different spin:
--> "The best optimization is simply not spinning things up."
At least for local development and testing, as made possible by LocalStack (https://localstack.cloud), among other local testing solutions and emulators.
We've seen so many teams fall into the trap of "someone forgot to shut down dev resource X for a week and now we've racked up a $$$ bill on AWS".
What is everyone's strategy to avoid this kind of situation? Tools like `aws-nuke` (https://github.com/rebuy-de/aws-nuke) are awesome (!) to clean up unused resources, but frankly they should not be necessary in the first place.
-
Getting Amazonka S3 to work with localstack
(For others who hadn't heard of it: localstack is
- LocalStack v3.0.0
- Localstack, a "AWS" local para desenvolvimento em cloud
-
Integration tests with AWS S3 buckets using Localstack and Testcontainers
LocalStack Website
- LocalStack: A functional local AWS cloud stack
-
Simulando a AWS no seu ambiente Local
O Localstack: https://localstack.cloud/, é um recurso que possibilita simular diversos recursos AWS (dynamoDB, s3, iam, cognito, ses), dentro da sua máquina, utilizando o docker.
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.
sst - Build modern full-stack applications on AWS
sst-start-demo - A simple SST app to demo the new `sst start` command
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
aws-sam-cli - CLI tool to build, test, debug, and deploy Serverless applications using AWS SAM
eks-anywhere - Run Amazon EKS on your own infrastructure 🚀
serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project
Appwrite - Build like a team of hundreds_