martian
LocalStack
martian | LocalStack | |
---|---|---|
2 | 154 | |
514 | 52,204 | |
- | 0.8% | |
6.4 | 9.9 | |
6 days ago | 1 day ago | |
Clojure | Python | |
MIT License | 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.
martian
-
Localstack – Local AWS Emulator
Or put the API definitions into some database (sqlite, datascript + nodejs or babashka or nbb), then you can decide what http library or mocked http solution would you like to use, eg https://github.com/oliyh/martian
Most of the code is just a thin veneer over that information...
-
Spec vs. Preconditions
There's a lot of concerns at the API edge of a system I would be looking at something like https://github.com/oliyh/martian this for an API and take half those concerns out of your current function
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?
snoop - Function instrumentation using Malli schemas.
Moto - A library that allows you to easily mock out tests based on AWS infrastructure.
aleph - Asynchronous streaming communication for Clojure - web server, web client, and raw TCP/UDP
sst - Build modern full-stack applications on AWS
serverless-localstack - âš¡ Serverless plugin for running against LocalStack
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
http-cron - Service / Clojure library to POST to HTTP endpoints at regular intervals
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
aws-cdk-local - Thin wrapper script for using the AWS CDK CLI with LocalStack
eks-anywhere - Run Amazon EKS on your own infrastructure 🚀
rcf - RCF – a REPL-first, async test macro for Clojure/Script
Appwrite - Your backend, minus the hassle.