the easier thing to do might be to run two workers, one to serve your site, and a different one to serve your API

I'll dig into that today, see how much effort it would be.

Is there a rough ETA for the open beta?

not publicly, no. FWIW here's the first Wrangler PR to support modules, though: https://github.com/cloudflare/wrangler/pull/1677

Would a pr against cloudflare/cloudflare-go with durable object api support be welcomed or too early/unstable at the moment? Planning on making some go tooling for myself before official wrangler support - happy to contribute back if it would help others

That'd be great. We shouldn't be making any backwards-incompatible changes to the API for configuring durable objects

Hi, is there a rough timescale for when durable objects are moving out of closed beta?

Soooo joining the Discord server also get’s you into the beta right? 😬🤗

we're making progress (and adding beta users gradually) but it'll be another couple months before open beta. We don't have a specific date, but rather a list of things that need to get done, like adding disks to expand capacity, and fixing a variety of bugs.

Greetings) also hi @User discord for dev community is an awesome idea

@User I suspect you're really annoyed with beta requests already, but... is there a way to know my position in the queue? 😉 (applied Nov7, email update from Dec3 says "expect an invite in January")

It's not a queue. We look at people's use cases and think about whether we're ready for those use cases, and also whether they are likely to be good tests of the system.

Oh, I see. Had a lot of time to think through the use cases (the API is really great, minimal and sufficient for a ton of ideas at the same time)

I think we've only been able to add like 1% of the people who applied so far. Lots and lots of demand, limited capacity at first. But that should change soonish.

I'm thinking of a distributed (offline-first) DB, using durable objects for sync\txn coordination, and then a Roam-like knowledge base and\or a low-code\no-code app dev env on top of it

there are lots of ways to store and sync data, but everything is on mobile now, with only occasional connectivity, and I found the low-latency coordination to be the bottleneck for years already

ie it's fine even if the objects occasionally get lost or smth 😄

low-latency is the missing part and a game changer here -- it really changes the user experience, otherwise CouchDB\PouchDB\Couchbase is more than enough since ~2006

(I'm pretty sure I haven't written anything sensible in the beta application form though :D)

@User does that ring any bells? plz plz 🙏

running everything thru CRDT in the browser\on mobile works too but it gets too CPU\traffic heavy

sounds interesting!

the part that gets particularly hard is where you want to synchronize schema changes and\or coordinate between different app versions

solvable too but really verbose\cumbersome on pure CRDTs so lies dormant on my hard drive since ~2018

cc @User ⬆

are you able to share any particular information about what use cases are being prioritized?

Unfortunately, not really. We don't have a list of use cases on hand but rather review everyone's requests on a case-by-case basis.

That being said, we're working hard to expand capacity so that soon enough we'll be able to welcome vastly more folks on to the platform, so stay tuned!

Is cloudflare working on database product based on durable objects?

Curious whether there is any best practise of troubleshooting durable objects?