I have detailed knowledge of dynamodb. This code does not properly mimic the service exceptions, input validations, eventual consistency, or edge cases. I would not feel comfortable developing against ministack or running tests against it. A lot of these services also have free tiers, so the use cases are quite minimal.
I'm frustrated with the Localstack license changes and will evaluate ministack.<p>But, for anybody else who needs a quick fix - you can pin to the `community-archive` tag and it should unblock you quickly:<p><a href="https://hub.docker.com/layers/localstack/localstack/community-archive/images/sha256-f72625f6b9546f1be730e9a9a9b1438c2298a4234634b1b823e3d3294e0b8bbe" rel="nofollow">https://hub.docker.com/layers/localstack/localstack/communit...</a>
I really don't see how any clone is going to manage to do what localstack couldn't - maintain compatibility with tons of AWS services while not getting paid for it. If this were viable, why would it not have worked before?<p>The only things I can think of are that perhaps LocalStack was just a mess of a codebase that couldn't maintain velocity or attract contributors, or it just failed to steward new contributors or some such thing.
<i>If this were viable, why would it not have worked before?</i><p>Because something wasn't in place to make it work. There are <i>millions</i> of examples where the second mover won, often because the first mover was too early, or the tech wasn't there to make it work, or the market didn't understand the value, etc.<p>In this case I imagine there are three massive benefits that you'd have over being the first mover:<p>- AWS is more mature and therefore moving slower, so it's easier to keep up.<p>- AI is useful for building 80% working code, so there's a lot less to do to keep up.<p>- There's a lot of devs looking for ways to move off Localstack due to the price change, which gives you (potentially) a pool of willing volunteers to contribute to an OSS alternative.<p>You can also learn from Localstack's open source version about what's needed, what works, what doesn't work, etc.
Personally, I would get value out of really solid compatibility of the base features of a few core services (sqs, s3, kms, and maybe dynamo are the main ones that come to mind) with a light weight gui interface and persistence.<p>If I’m getting into esoteric features or some “big” features that don’t make sense locally, then I just spin up a real dev account of aws, so I know I’m getting the real experience.
> getting into esoteric features<p>The problem is that everybody needs different "core" features<p>> > compatibility of the base features of a few core services (sqs, s3, kms, and maybe dynamo are the main ones that come to mind)<p>For instance, I don't care about any of those features at all. But I would care a lot about EC2, RDS, and ElastiCache Redis
Interesting — those are the ones that depending on the case, approximating them with local redis/postgres/vms without the AWS specific APIs on top is often good enough — because my app is just talking to them over native protocols anyway.<p>Or I am doing something so specific, that a local emulation of the aws api isn’t ever going to be good enough, so there’s not a lot of point in trying. For example, writing code that handles automatically spinning up RDS instances from an RDS snapshot — a local emulation of that process is going to be so far off from what would actually happen no matter what they do.
I'd put ALL the ones listed above: SQS, S3, KMS, DynamoDB, EC2, RDS, Redis in the required "core" services column, and also throw in IAM, SNS, and SecretsManager as well. Those are all table stakes imho.<p>I'm using all of the above in LocalStack today. Frankly, I don't believe this is as "impossible" a task as several in this thread are insinuating. It's the type of rote work you can delegate to AI to build these days, as observed in this OP.<p>Building a test suite to validate the state-transient mocks in question against the real deal is not difficult. Only annoyingly expensive (in time and money) if run often, which is exactly the problem they're solving.
Hello! We won't have the broad coverage that Localstack has... we're not aiming to be the "next Localstack"... just want to keep the core services that were available for free in the LS community up to date. If you’re looking for larger services like MWAA, sorry, but we won't be supporting them.... Most core AWS services don't receive many updates anyway (their APIs don’t change drastically or frequently)
> We won't have the broad coverage that Localstack has... we're not aiming to be the "next Localstack"<p>you should tell that to the LLM that writes your website:<p>> MiniStack is your free, MIT-licensed drop-in replacement.<p>is it a drop-in replacement, or not?
If you’re looking for a Localstack alternative, it’s often because you were using the community tier... In that case, Ministack can serve as a drop-in replacement... otherwise, the price reduction in LS might already address your needs
That's true if you assume making these things is manual work. But of course with well documented API service and AI coding tools, making a functional local equivalent of any given service is not all that hard.
"LocalStack was just a mess of a codebase" - very true.<p>I do think there's potential to semi-automatically create a compatible suite of services, but it'll require some very talented use of LLMs and some novel testing approaches. Not something I want to sign up for.<p>I evaluated Floci, but that has the typical issues you'd expected with freshly minted vibe code.
idk maybe AWS should create one?<p>I mean, if we can use "virtual-AWS", it would dramatically lower entry-barrier for devs/companies who are scared of "tales of huge aws bills" and such
I suppose (among many other things) LLMs are changing this. We no longer need that many contributors when we can use AWS docs, intercept AWS API calls and give it to AI agent to mimic. Of course, contributors are still needed for maintaining tests and validations.
The real issue with LocalStack was always drift. Tests pass locally, then something breaks in staging because the S3 response format is slightly different or DynamoDB throttling doesn't match. After getting burned enough times we just switched to short-lived real AWS environments for integration tests. More expensive, but way fewer surprises in prod.
i would imagine localstack is a sniff-test - aka, if it doesn't pass localstack, you don't run the more expensive real AWS integration test. In other words, like food, you don't eat the cost unless it passes the sniff test.
[dead]
Any project with Claude’s signature misaligned ASCII diagram just screams DON’T USE to me. If you can’t even bother to read your damn generated README, how do I know you have QC’ed anything else? At the very least supported features claimed in README / on website could be totally fake, which is extremely common among all the vibed Show HNs.<p><a href="https://github.com/Nahuel990/ministack/blob/a1b1d20a27d2238dd7b776eeb426e93d816e5c09/README.md#architecture" rel="nofollow">https://github.com/Nahuel990/ministack/blob/a1b1d20a27d2238d...</a>
I love how a comment pointing out glaring lack of human review of this project (with clear evidence) is flagged to death. With zero counter-argument no less. Can’t wait for the bright future of vibed crap with zero human quality control getting hacked every day.
But brother, he is shipping at inference speed!
ASCII with rounded corners is already a red flag, let alone not being able to check if it's aligned. Claude LOVES these.<p>Something more realistic would be:<p>+-----+<p>| foo |<p>+-----+
Yeah. Could at least run a formatter on it afterwards... You can even configure a hook for Claude to do that.
We live in the golden age of slop. It seems a surprisingly small number of people have the visceral AI disgust response.
Ugh, I hadn't heard the news about the LocalStack licensing changes. I had some great results building AWS services for local dev as well as CI/CD and testing in GH actions with LocalStack in previous jobs.<p>I secretly always hoped Amazon would buy out LocalStack and make it the official free local development environment for AWS work, but I guess it probably would reduce revenues spent on AWS based dev and test environments. The compatibility with the AWS CLI was mostly excellent in my experiences.
Unclear what LocalStack's end game is tbh. My company has an active enterprise license atm so their recent changes won't affect me in the short term at least. As of writing I'm still a happy user of LocalStack. Disappointed with their overall direction, but I hold no ill will and I'm sure they had their reasons. I wish them luck.<p>Hopefully this change was not just an short term attempt to lock in current enterprise customers by shoring up existing income streams. That'll only work in the VERY short term.<p>It's not difficult to forsee the inevitable customer drain to free competitors or private one-shots easily produced by genai from publicly available AWS SDK code. Maybe they're already feeling that pressure and that's all this change is. I hope not.<p>AFAICT, they have no appreciable moat to retain customers long term. For example, I have absolutely no interest in their "Pods" or even their console UI, so thosr aren't keeping me around forever. For their sakes I hope they're still shopping themselves around and didn't take some VC poison pill with preconditions for killing the community edition. Really It's anyone's guess though.
> The compatibility with the AWS CLI was mostly excellent in my experiences.<p>Interesting, I've had the opposite experience. Every single AWS service I've ever tried to build tests around with LocalStack has run into compatibility issues. Usually something works in LocalStack but fails when it hits the real endpoint.<p>I guess the CLI itself has mostly worked, its more the LocalStack service not behaving the way the real service is documented/works.
Got any concrete examples? I've been happily using LocalStack for roughly a decade now and haven't run into a single compatibility issue, aside from the obvious missing of net new services for the first N months after AWS product launches. Things like AppConfig, etc, but those gaps got filled in time. They clearly prioritized the 95pct/most used features of each service first though. There's a long tail in some AWS services, as one might expect. I've never used any of the more esoteric AWS feature sets of any of their services. Those are the things that tend to end up deprecated. So requiring those long tail featur sets may be the simple answer to having very different experiences.
Another alternative, earlier on HN: <a href="https://news.ycombinator.com/item?id=47420619">https://news.ycombinator.com/item?id=47420619</a>
I liked the transparency: "Built entirely with AI by Jack Danger | All prompts saved in prompts/"
Thus far I've tried that (rejected), Floci (not great), and now looking at this.<p>This one is 7 days old.<p>I'm eager to have a localstack replacement, but these are a long way off from being mature enough. I suppose this is just the new state of software? Shiny website, big claims, AI coded, insufficiently tested.
Out of curiosity, why did you reject Floci? It lacked some feature I needed, so I just went ahead and added them. My needs were not that complex and it has patterns to test that implementations match AWS. I agree it’s lacking things, but the bones aren’t that bad.
> Copyright (c) 2024 MiniStack Contributors<p>Already lying or totally unreviewed AI slop ?
What’s the gcp equivalent
[dead]
[dead]
for most teams the pain was not missing features -- it was drift. you build against the emulator for months, then hit some edge case in prod where the S3 response format differed slightly or DynamoDB error codes were not qui