LocalStack
homepage
Our great sponsors
LocalStack | homepage | |
---|---|---|
154 | 16 | |
52,055 | 11 | |
1.1% | - | |
9.9 | 7.2 | |
7 days ago | about 1 month ago | |
Python | SCSS | |
GNU General Public License v3.0 or later | 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.
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.
homepage
-
Is Nestjs easy to understand for frontend developer who is good at Typescript, reactjs and familiar with express?
I highly recommend, with these types of credentials, go serverless and use https://sst.dev/ with https://nextjs.org/ . Stupid simple deployment, and SST’s (reasonably priced) paid arm, https://seed.run/, for ci/cd and deployment including great stage management, and nearly free logging and error observability.
-
Is anyone successfully using the CI/CD offering from serverless.com?
I've used seed.run with the Serverless Framework for 4-5 years. As I don't deploy to much I've stayed with the free tier and it all works perfectly. Try it out it won't disappoint.
-
How much vendor lock-in is there in the NextJS/Vercel ecosystem?
They have, at least SST, visit seed
-
What tech-stack to use for a solo dev that can prioritize product iteration and scale?
The backend is built with serverless.com (lambda, dynamodb, sqs, appsync). The good thing is that all the backend is stored in a file and you can deploy multiple stacks on the same account using seed.run . You don't really need EC2/Fargate when you have lambdas and you know that most of the time will be idle time. The same with cache I wouldn't think of it right now until you see the workload you are facing. Dynamodb once you understand it and have a proper design it's the fastest thing you can have. On my appsync calls I'm using Dynamodb as a cache because it's cheaper...
-
Do some developers actually, REALLY, have no local environment and run everything in AWS? Is the individual cloud dev environment a real alternative to having things running locally?
I run my personal project on AWS. I has been running for 4+ years now and I never had a local environment. I took the serverless route. That is appsync, lambda, dynamodb, sqs to build the stack. I'm using serverless.com to have all the resources defined in a yaml files which will deploy multiple stacks. I'm using seed.run to manage that part because it's much more simple than to do it manually.
-
Best managed graphql service for database + search?
How do you deploy your services on AWS? I'm a solo developer and have no issues with my backend. I use the Serverless framework so all services, lambdas, configurations is on a repository on git. I do all the deploys to a dev environment where I test my code and later on I deploy with a PR to my prod environment thanks to seed.run.
-
Structuring a Real-World Serverless App
Your repo setup can look different, but the general concept still holds true. You have to figure out if a file change affects an individual service, or if a file change affects all the services. The advantage of this strategy is that you know upfront which services can be skipped. This allows you to skip a portion of the entire build process, thus speeding up your builds. A shameless plug here, Seed supports this and the setup outlined in this post out of the box!
-
Working with Lambda Code
I use serverless.com framework with tests and deploy with seed.run. So I don't ever touch a Lambda in production. I also have 2 environments, one for testing and the other for production.
-
I have a serverless application with multiple services or stacks which behave as a microservice , I have a build.sh file which allows me to deploy specific service. Now , I want to automate my deployments using gitlab/github but only deploy specific stacks
I'd use seed.run . You can deploy multiple stacks on parallel or with dependencies. You can deploy from github ( 100% sure ) from gitlab I'm not sure. Worth checking it. I'm using the service for free and haven't had any issue.
-
What do you like/dislike about AWS services? What are the most common problems?
Building on top of it requires some knowledge but for me it has been worth it. I use serverless.com to manage all the infrastructure as a CF template. This has the benefit that I can deploy multiple test environments at will. I'm also using seed.run to do all the CI/CD ( also for free ) and doing all the monitoring with lumigo.io . And I build single pages applications that use Netlify.com to handle at that part. I do it to avoid less things to manage on AWS directly when the service is free (again) and really easy to use.
What are some alternatives?
Moto - A library that allows you to easily mock out tests based on AWS infrastructure.
sst - Build modern full-stack applications on AWS
serverless-plugin-warmup - Keep your lambdas warm during winter. ♨ [Moved to: https://github.com/juanjoDiaz/serverless-plugin-warmup]
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
esbuild - An extremely fast bundler for the web
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
Previous Serverless Version 0.5.x - ⚡ Serverless Framework – Use AWS Lambda and other managed cloud services to build apps that auto-scale, cost nothing when idle, and boast radically low maintenance.
eks-anywhere - Run Amazon EKS on your own infrastructure 🚀
serverless-bundle - Optimized packages for ES6 and TypeScript Node.js Lambda functions without any configuration.
Appwrite - Build like a team of hundreds_