eucalyptus VS LocalStack

They rebranded: https://github.com/corymbia/eucalyptus#readme but development is either happening "offline" or they've stalled development because https://github.com/Corymbia/eucalyptus-blog/blob/master/cont... is the most recent blog update

It's also a beast to even compile and package, to say nothing of actually deploy

The website is still up and points to a fork on GitHub:

- https://docs.eucalyptus.cloud/eucalyptus/5/install_guide/int...

- https://github.com/corymbia/eucalyptus/

There are quite a few moving parts. I think I got stuck around just comprehending the networking bits.

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:

Acesse o site da LocalStack e faça login.

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.

(For others who hadn't heard of it: localstack is

LocalStack Website

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.