merloc
LocalStack
merloc | LocalStack | |
---|---|---|
5 | 154 | |
193 | 52,204 | |
0.0% | 0.7% | |
0.0 | 9.9 | |
over 1 year ago | about 5 hours ago | |
TypeScript | 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.
merloc
- MerLoc
- Show HN: I made an IDE plugin for AWS Lambda local dev, debugging and hot-reload
-
Show HN: I made a local development, debugging and hotreload tool for AWS Lambda
Yes, there any many serverless people looking for Node support. Could you please thumbs-up its feature request here: https://github.com/thundra-io/merloc/issues/1
- MerLoc: Live AWS Lambda function development and debugging tool
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?
merloc-java - MerLoc is a live AWS Lambda function development and debugging tool. MerLoc allows you to run AWS Lambda functions on your local while they are still part of a flow in the AWS cloud remote.
Moto - A library that allows you to easily mock out tests based on AWS infrastructure.
chrome-aws-lambda - Chromium Binary for AWS Lambda and Google Cloud Functions
sst - Build modern full-stack applications on AWS
serverless-next.js - âš¡ Deploy your Next.js apps on AWS Lambda@Edge via Serverless Components [Moved to: https://github.com/serverless-nextjs/serverless-next.js]
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
eks-anywhere - Run Amazon EKS on your own infrastructure 🚀
Appwrite - Your backend, minus the hassle.
testcontainers-python - Testcontainers is a Python library that providing a friendly API to run Docker container. It is designed to create runtime environment to use during your automatic tests.
AWS SDK for Ruby - The official AWS SDK for Ruby.
unleash - Open-source feature management solution built for developers.