slowpokefs
LocalStack
Our great sponsors
slowpokefs | LocalStack | |
---|---|---|
1 | 154 | |
13 | 52,145 | |
- | 1.3% | |
0.0 | 9.9 | |
almost 10 years ago | about 22 hours ago | |
C | Python | |
GNU General Public License v3.0 only | 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.
slowpokefs
-
Crazy fast build times (Or when 10 seconds starts to make you nervous)
One thing I saw was someone logging all system calls their software generated and comparing that between runs. They'd been bitten by some minor library upgrade that had changed directory scanning which caused huge multiples of normal latency which on an SDD wasn't noticeable but on an HDD went from trivial to insane.
That was handy because it didn't actually involve testing on a slow device but mostly showed what we needed to know.
There are tools like https://github.com/schoentoon/slowpokefs which try to make your fast storage act like a HDD which could be better for black-box testing.
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?
safeql - Validate and auto-generate TypeScript types from raw SQL queries in PostgreSQL.
Moto - A library that allows you to easily mock out tests based on AWS infrastructure.
safeql - Composable / async / functional / type-safe / parallel-pipelined queries and relations without SQL injection or N+1s.
sst - Build modern full-stack applications on AWS
compiler-benchmark - Benchmarks compilation speeds of different combinations of languages and compilers.
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
ctl - My variant of the C Template Library
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
icecream - Distributed compiler with a central scheduler to share build load
eks-anywhere - Run Amazon EKS on your own infrastructure 🚀
Appwrite - Build like a team of hundreds_
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.