azure-service-bus VS LocalStack

There has been a ticket open requesting an Azure Service Bus emulator for FIVE YEARS lolsob https://github.com/Azure/azure-service-bus/issues/223

Which is too bad, because ASB is awesome, IMO the best Azure service.

Sadly it’s a factor with Azure service bus which suffers from both, not the best local testing experience & lock-in. github issue for more info.

Assumin *he means this https://github.com/Azure/azure-service-bus/issues/223

We would like to share a link to Microsoft Azure Service Bus GitHub. Most of the implementations of either the publisher or the subscriber were inspired by this documentation, so make sure you check it out! If you have any questions, please write them down below.

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.