Celld: Self-hosted, distributed Durable Objects
celld.dev> each cell is one sqlite database
I just can't wrap my head around this. I know there is probably some very strongly motivated engineering reason like "we want objects to be isolated", but I just can't agree with this
Isn't this the natural continuation of:
server = server → server = vm → server = function → server = block
idk, Cloudflare is also struggling to explain durable objects for years, maybe this would help https://flaviocopes.com/celld/
Self hosted, durable objects?
Are they stored in files? On my filesystem?
sure, when you run the server locally.
> The bucket is the coordinator — no membership protocol, no failure detector, no consensus.
Sorry, but for me, even being a heavy user of coding agents at work, LLM-isms like this on your home page make me less trusting in the care gone into the project.
Copy aside I think the approach is similar to https://turbopuffer.com/blog/object-storage-queue
The quiet improvements to S3 over the last 3 years like conditional puts unlocked a lot of use cases not previously feasible