Why we're moving off Cloudflare Durable Objects

zuzululu

> What we built > Each organization gets one host process (Bun) on Fly Machines for all its containers. Well that is an instant nope from me. Fly.io's uptime/availability isn't something I trust and I am not alone. Part of what makes cloudflare durable objects great is the sheer availability and consistency at a true global scale

chandureddyvari

Took me a bit to understand what Wire does, but then it clicked. we’ve built something similar at a smaller scale inside R2, though right now it’s only for .md files. I can see this becoming much more useful once the docs get heavier: large PDFs, XLSX files, images, etc. At that point you probably need embeddings, reranking etc. But I think agents are smart enough to write scripts to retrieve what they want if we run them on a sandbox(which we are trying to do currently). bookmarking this for now. Good write-up though!

stephantul

Why do all this work and then let an ai write the blog post.

debo_

The objects are durable, but not endurable.

PUSH_AX

The thought of moving back to Fly after CF is completely absurd to me, each to their own. May your downtime be minimal...