Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • For a hot minute Eucalyptus https://www.eucalyptus.cloud was amazing - even matching aws bugs to keep compatibility. Wish it had rue support/resources to keep going. Maybe a viber will pick up and get it more up to date.
  • I've looked into developing "digital twins" of APIs that I rely on, similar to the StrongDM pattern, but the models talk me out of it every time. The rationale is that there could be subtle differences or drift between the behavior of the real service and the mocked API. So you may think you're on solid ground, but once you switch to prod, you could see show-stopping differences.

    I think if I was doing evals on the way an agent interacts with a service (e.g. Slack) the digital twin could make sense, but for rapid iteration or testing, it might not be what you want.

  • I was never happy with how heavy LocalStack was, so I'm going to try this for my next green field cloud app.

    I think having such emulator being lightweight and quick to run becomes more important in AI coding/worktree-based workflows where it's important to pre-setup the worktree with dependencies and dependent services on local ports.

  • As a speaker of Romanian, loving the name

    ("floci" means "pubes")

  • Would someone be interested in this but intended for production? Im already running a whole bunch of cloudflare and AWS services in my own AWS fake and it works surprisingly well! :)
  • Been using it for a while to run integration tests with Testcontainers [1]. It's very good and much more lightweight than Localstack.

    [1]: https://testcontainers.com/

  • Both localstack and floci live in this weird spot where for a lot of my applications, all the cloud-vendor specific stuff is abstracted out anyway. So the only time I need to touch the cloud is for testing the abstractions and do end to end testing. The abstractions can be tested against real cloud APIs as it is generally cheap to do and provides the highest fidelity results. End to end testing includes testing against a production-like environment, so again, more bang for your buck to just test against the cloud.

    I’ve definitely reached for these local cloud tools from time to time, but in a well-architected piece of software, you aren’t getting that much value from them. Either you don’t have a hard cloud dependency, or you want a high fidelity test of a specific cloud dependency.

  • The cool part of this is it’s an example of what’s possible with a community of users armed with AI.

    Many users, (myself included), had need to test cloud stuff locally, but had no tool to do so. Localstack exists, but it started rug pulling the free tier and they didn’t support all the features.

    Meanwhile, Floci makes it easy to write your own cloud compatible test suite, then implement the feature to match. I was able to get a good enough coverage on a few features created in a weekend on the $20 tier of Claude to make it useful to me, then others picked up the work to round it out.

    It’s really cool to see it grow.

Explore Birbla archives