Join the discussion

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

  • Hacker News
  • How does it compare to celld?
  • 100ms for a write - not usable for anything beyond toys.

    I mean we have https://github.com/denoland/celld - with a known good open source history. Durable writes there are as low as 1ms.

  • Great! Let’s have more cloudflare alternatives
  • This looks really nice! How would you compare it to Rivet? I think they were also originally pitched as an open source version of durable objects: https://rivet.dev/actors/compare/rivet-actors-vs-cloudflare-...

    Also are you able to self-host this outside of GCP (from the docs it seems like it is locked to GCP but I'm not that familiar with it so maybe not)?

  • How do you compare to Azure Durable Functions, Temporal, AWS Lambda Durable Functions?

    Can't Durable Entities meet the same use cases?

    EDIT: Of course I am not talking about the difference in OSS vs not. Rather I'm interested in the difference in use cases and capabilities. Some of the aforementioned have ways to run things locally as well, though they are designed as distributed cloud-based PaaS services.

  • Looks great but one of the common problems with the virtual actor model is state query. It's all well and good to have nice separated state dbs but for most use cases that means further double up on storing the state again in another database that can query it. I don't think anyone has come up with a nice solution for this problem without using a loose document database, but even then actors can change their schema.

    Perhaps emitting versioned domain events transactionally with the actor state is an option without prescribing an exact solution.

Explore Birbla archives