| ▲ | operator_nil 13 hours ago | |
This is exactly what I was waiting for. Although I love localstack and am grateful for what they have done, I always thought that an open community-driven solution would be much more suitable and opens a lot of doors for AWS engineers to contribute back. I’m certain that it’s on their best interest to do so (specially as many of their popular products have local versions) It’s a no-brainer to me as AI adoption continues to increase: local-first integration testing is a must and teams that are equipped to do so will be ahead of everyone else | ||
| ▲ | drzaiusx11 25 minutes ago | parent | next [-] | |
How is it in AWS' best interest to provide support or changes for a FOSS clone (albeit with ephemeral storage)? I believe that providing locked down local-first containers themselves for various services (which they do for services like ddb) would make more sense. I'm sure no one at AWS would take a bug report seriously saying random FOSS thing doesn't work with their official client sdks... | ||
| ▲ | zach_vantio 13 hours ago | parent | prev [-] | |
100% this. especially with agentic workflows actually mutating state now. local testing is the only safe way to see what happens when a model hallucinates a table drop without burning an actual staging database. | ||