3 ms·
Show HN: Hiraeth – AWS Emulator
With the recent changes around Localstack pricing/licensing I've been hunting for alternatives. I decided that it might be a fun experiment to try rolling my own. SQS is a service I use heavily so I chose that as the first service to implement. I have more services planned and in development.
A few things I think are cool:
4MB Docker Image Size
Instant Startup
AWS Sigv4 Authentication
A little admin UI that can be helpful for development/troubleshooting
Most of the SQS API implemented, the rest will soon follow :)
- Carrok 5mo agoLooks cool! Now add (simulated) billing. ;)
- great_psy 5mo agoWhat kind of things would you use this to simulate ? Is this to make sure services are wired up with permission and communicate properly before you deploy or what is the use case ? Also, why not have a dev environment where you can test things on the real thing (ideally with smaller size instances to save $)
- giza182 5mo agoIntergration testing is one. You can run this in your ci/locally to speed up tests. Or just for local dev. We do this with localstack[1] [1] https://www.localstack.cloud/ https://www.localstack.cloud/
- ozarkerD 5mo agoYep integration is my use case as well. It’s nice to not have to worry about setting up real infrastructure for testing client code, parallel execution if you’re on a team, clearing out state each run, etc…
- leetrout 5mo agoAnother SQS stand-in is smoothmq https://github.com/poundifdef/smoothmq https://github.com/poundifdef/smoothmq
- michalc 5mo ago> the rest will soon follow If you’re looking for requests ;-), I would love an ECS (and specifically Fargate) emulator that actually ran Docker containers locally as though they were in ECS
- ozarkerD 5mo agoThat's a great idea i've had floating around in my head too!
- slava_vechir_2 5mo agoWorks perfectly.
- ozarkerD 5mo agoAwesome, appreciate the feedback!
- MouadNos 5mo agowhat compatibility surface is prioritized first for SQS edge cases
- ozarkerD 5mo agoGood question. I'm driving mostly off of my own use cases currently, so AWS SDK/CLI/Terraform compatibility. Response formats, codes, messages are best effort, there's a little work to be done there still. There's some gaps around request validation still too. The idea is to build up a good suite of integration/regression tests as cases are identified by myself or the community (if there is one) through development.