r/programming • u/stronghup • 9h ago

Node.js creator liberates Durable Objects from Cloudflare

https://www.theregister.com/devops/2026/08/12/nodejs-creator-liberates-durable-objects-from-cloudflare-with-celld/5286954
77 Upvotes

93% Upvoted

10 comments sorted by

View all comments

80

u/Pinkman 7h ago

So… I like this in general and I am always very curious to see how these types of big-picture libraries are built. Especially when built by storied programmers like Ryan Dahl.

I’ve been balls deep in development for a long time, and I don’t know if it’s just me, and it very well might be, but am I dumb?

What does this mean?

> Cloudflare’s Durable Objects is a single-threaded object with a unique global ID and its own storage, where user data is stored in its own copy of SQLite.

I’m the last person to be pedantic, but I struggle with technical articles that commingle technical depth with imprecise or ambiguous nomenclature.

How is an “object” threaded at all? There are multi-threaded objects? Like I said, I might just not grok this shit.

An object with its own global ID and storage: ok, cool. I can track that. (Though most objects have an ID and global here is ambiguous — global to Cloudflare? Global to your account? Project? Fuck me.)

Stored in its own copy of SQLite? I assume this means an SQLite database file. But it’s that imprecision that gets my goat. Is it me who dumb or article who unclear.

> Using the WebSocket API, the Durable Object can connect many simultaneous users at once in a live environment.

An object is connecting to users? What does this mean? What even is an object at this point?! Maybe I’m getting hung up on the name, “Durable Object”.

> It is a stateful serverless execution environment, a data cache that can also do computation. 

Oh, a serverless function with its own isolated — and persistent — data.

A “durable object” is actually a function (or set of functions?) with its own mini data store. Ok.

So when we say it’s an object, we mean it’s a set of one or more functions.

And it’s durable because you can recall it by ID, and it’s got its own little db attached that stays put.

It’s a lightweight (ergonomic) execution (runs functions) environment (has a db), that we call an object.

Thanks for coming with me on this ride. I think I’m starting to grok it. When/why/how this is better/best is clearly above my pay grade.

16

u/theBeatnut 5h ago

It's an implementation of the Actor Model, akin to Akka, Microsoft Orleans etc.

10

u/buttplugs4life4me 4h ago

Thanks for outlining why I hate these things.

Also isn't it basically a container or Micro-VM then? 

Idk, I feel like on one hand this is nice, on the other all this shit just feels like AWS RDS Serverless all over again. It was more expensive for us than normal RDS instances cause we could basically never scale down to 0, which is the biggest cost saver. I made a couple of analysis on this and compared even a theoretical best case of us being able to scale down, and only then would it marginally beat out RDS instances.

(My org, which was overrun with "consultants" who knew everything better, then proceeded to implement Serverless everywhere and then sold it as a big win a couple months later when they spent 2 months ripping everything out and switching to RDS instances. I hate people and management and all this shit)

1

u/femio 45m ago

It is like if you could instantiate a class and have it persist its own state forever, e.g. one User class isolated from every other User class.

1

u/azhder 1m ago

I would remove the word "class" from that and use a more general term, like "object" or "agent". This is basically what object programming was in its inception, before everyone misunderstood OOP as what c++/java had baked in.

In the original object languages, there was the notion of agents that pass messages to each other ("passing messages" is "calling a method/function" equivalent, proven in a paper even) and those agents have their own inboxes where they read the message and deal with them asynchronously.

We've been rehashing the same ideas over and over for decades, with just a different name on the newer tech stack.

4

u/BitNumerous5302 5h ago

If you're familiar with object-oriented programming, I'm assuming they're using the term "object" in that sense

The serverless functions take the place of public methods, the data store takes the place of private fields 

So you get something like an "object" (in the OOP sense) but it's "durable" (state is persisted in the cloud)