Has anybody tried this and can share their experiences? It sounds really cool, but it's usually the edge cases that determine whether something like this is actually good or not. Thanks!
Just waiting on edge containers [1] now. Yes, I know the caveats, that it's not for lifting and shifting existing web apps. But I have a backend processing use case that would be a good fit.
Quick plug I'll drop in here (I manage Cloudflare's Developer Advocacy team) - in addition to Durable Objects reaching GA, we also released a great open-source codebase today to help scale your Durable Objects-based projects.
It has built-in sharding and communication between connections/shards - basically how we would recommend people build with DO if they want to hit the ground running.
While it could be interesting, it's kind of expensive to have servers in all of those countries globally, and manage all that required software. So pre-made services like Durable Objects make it much more affordable.
Their chat demo is very nice, i'm not a javascript or a webdev guy, but i'm use to see bloat everywhere whenever someone mentions web stuff
> wrangler publish
> What are the dependencies?
> This demo code does not have any dependencies, aside from Cloudflare Workers (for the server side, chat.mjs) and a modern web browser (for the client side, chat.html). Deploying the code requires Wrangler.
I wish more people would care about that kind of details more
In all honesty, I do it this way because I hate reading. Like really, really hate it. It just seems way more comfortable to build what I need off the base platform APIs I've known for decades than, like, read an intro guide on how to use the latest library or tool or framework or whatever. Probably not the best way to operate as an engineer but I'm glad it ended up making this demo easier to follow! :D
(I'm the tech lead of Cloudflare Workers and I also wrote that chat demo.)
This seems like it could be a great platform to flesh out the collaborative Svelte REPL I’ve been working on. It’s using CRDTs over websockets with YJS driving Monaco, and I’ve been fiddling with different ways to keep track of rooms and users while keeping it serverless on the JAMStack. I’ve got Supabase handling auth and data storage, but this could be great glue for the final pieces if I’m understanding DO correctly, and even replace a lot of the need for Postgres outside of Auth.
16 comments
[ 3.8 ms ] story [ 45.7 ms ] thread[1]: https://blog.cloudflare.com/containers-on-the-edge/
It has built-in sharding and communication between connections/shards - basically how we would recommend people build with DO if they want to hit the ground running.
Check it out on GitHub! https://github.com/cloudflare/dog
https://github.com/canonical/dqlite
https://github.com/rqlite/rqlite
https://github.com/Expensify/Bedrock
https://datacadamia.com/dit/kafka/connector/sqlite_distribut...
> wrangler publish
> What are the dependencies?
> This demo code does not have any dependencies, aside from Cloudflare Workers (for the server side, chat.mjs) and a modern web browser (for the client side, chat.html). Deploying the code requires Wrangler.
I wish more people would care about that kind of details more
Well done
In all honesty, I do it this way because I hate reading. Like really, really hate it. It just seems way more comfortable to build what I need off the base platform APIs I've known for decades than, like, read an intro guide on how to use the latest library or tool or framework or whatever. Probably not the best way to operate as an engineer but I'm glad it ended up making this demo easier to follow! :D
(I'm the tech lead of Cloudflare Workers and I also wrote that chat demo.)