[flagged]
MiniStack (replacement for LocalStack)
51–60 of 88 posts
Re: MiniStack (replacement for LocalStack)
#52I 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.
Mostly I think its not about cost, it is about iteration speed and ability to run in CI environments fast.
Re: MiniStack (replacement for LocalStack)
#53Earlier quoted context omitted.
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.
[flagged]
I am currently implementing S3, with correct error handling for edge cases. Its been about a month and I have almost the whole API surface done, with some gaps (you actually need a broader surface eg some IAM, KMS encrytion needs a persistence layer so only done sse-c so far). Close to the point where you could drop it in as a local emulation tool, its a sub 9MB binary (Rust).
Literally as I write this the AI code review said "suspended-bucket current-version selection is still wrong when the numbered version and the newer null version land in the same millisecond." - thats the level of detail you have to deal with.
Re: MiniStack (replacement for LocalStack)
#54Earlier quoted context omitted.
"LocalStack was just a mess of a codebase" - very true. 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. I evaluated Floci, but that has the typical issues you'd expected with freshly minted vibe code.
idk maybe AWS should create one? 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
It hasnt really been a barrier to entry though has it, cloud adoption is doing just fine.
Re: MiniStack (replacement for LocalStack)
#55Earlier quoted context omitted.
[flagged]
I am currently implementing S3, with correct error handling for edge cases. Its been about a month and I have almost the whole API surface done, with some gaps (you actually need a broader surface eg some IAM, KMS encrytion needs a persistence layer so only done sse-c so far). Close to the point where you could drop it in as a local emulation tool, its a sub 9MB binary (Rust). Literally as I write this the AI code re…
[flagged]
Re: MiniStack (replacement for LocalStack)
#56FR: real cost simulator
Re: MiniStack (replacement for LocalStack)
#57Earlier quoted context omitted.
I am currently implementing S3, with correct error handling for edge cases. Its been about a month and I have almost the whole API surface done, with some gaps (you actually need a broader surface eg some IAM, KMS encrytion needs a persistence layer so only done sse-c so far). Close to the point where you could drop it in as a local emulation tool, its a sub 9MB binary (Rust). Literally as I write this the AI code re…
[flagged]
Not really, the main thing they could change is the order in which errors are checked when there are multiple errors, but even a lot of that is not likely to change, eg html based stuff comes first. There are actual reasons for a lot of the subtleties, plus they have to have a stable contract for all the success cases as people rely on it. And its not hard to update, I have 800 or so tests against AWS that run in a few minutes.
Re: MiniStack (replacement for LocalStack)
#58As other commenters have noted, this looks like AI slop. Why is it on the front page?
If you go on Reddit, there are at least a dozen AI "vibe coded" shitty local stack alternatives being posted daily. Whats special about this??
Re: MiniStack (replacement for LocalStack)
#59Earlier quoted context omitted.
Maybe that visceral response being against the rules (assume good faith) and actively being punished explains the small number of people doing it?
My visceral AI disgust response here is just a subset of my more general lazyly-slapped-together-without-sufficient-testing-or-other-review disgust response. If it doesn't look bad in that way, whether hand-made or ghostwritten, then I'll not react to it that way. But if someone can't be bothered to do a simple clean-up pass on that documentation, what mess could they have left in the code too? As far as I'm concerne…
>Acting in good faith works both ways, or it doesn't.
Well said, polluting hacker news with low effort slop for self promotion cannot be good faith. The rules are enforced on commenters but good faith is not expected for submissions somehow
Re: MiniStack (replacement for LocalStack)
#60The 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.
[dead]