Nathan Flurry 🔩

Durable Objects SQLite is also quite nice!

damn this thing should replace product managers

Oh no hahaha, that's what I get for copying grammar proofs out of Claude

I promise this post is 100% non-AGI hand-written otherwise 😅

New blog post dropped: why Traefik was the slowest part of our stack & how we rewrote it from scratch in Rust 🦀

My 2025 H2 goal is to get really good at technical writing – this is the first of many posts to come

I loved writing every word of this, I hope you enjoy it too ⬇️

YouTube video by Rivet Introducing Rivet Studio

Announcing: 🎨 Rivet Studio v1.0

A powerful development environment for @rivet.gg Actors & Cloudflare Durable Objects for realtime apps.

🧠 View/edit actor state
📞 Test RPCs like Postman
🔍 Explore live connections
🔥 Hot reload everything

→ studio.rivet.gg

youtube.com/shorts/LXUNq...

this is so cool! how was your experience with turso?

📝 @threepointone.bsky.social ask and ye shall receive 5,041 words

rivet.gg/blog/2025-03...

i hear this a lot! which of the technical limitations have you ran in to?

Docs: actorcore.org/introduction

GitHub: github.com/rivet-gg/act...

Clip: www.youtube.com/clip/UgkxawK...

Thx @jross.me for surfacing the clip

"The only people I know actually getting Durable Objects working are Cloudflare employees" - @t3.gg on stream

If you're curious about Durable Objects but not the complexity:

ActorCore.org has been my obsession for the past month to make DO as simple as possible

Example code & GitHub below ⬇️

@rivet.gg ActorCore spotted in the wild 👀

Rust - ActorCore

Docs: actorcore.org/clients/rust

GitHub: github.com/rivet-gg/act...

New in ActorCore v0.7.4: Rust client support 🦀

$ cargo add actor-core-client

It's:
✅ stupid fast
✅ runs anywhere
✅ ready to ship

Check out the docs & repo 🧵

ActorCore - ActorCore Stateful, Scalable, Realtime Backend Framework

Docs: actorcore.org/introduction

GitHub: github.com/rivet-gg/act...

🤌 i talked to sooo many devs to refine ActorCore v0.7's new api. the same code in Durable Objects is now 4x longer

✅ pure functions, no more `extends Actor`
✅ split actors x-file
✅ short & fun to write

try this thing and tell me it's not the best way to write realtime apps

🔶 ActorCore 0.6.0 just shipped with a super slick create-actor cli and overhauled docs

create your first stateful, scalable, realtime actor with:

$ npx create-actor@latest

oh dang, some rando posted our blog to HN and it’s climbing.

give it a read + an upvote!

news.ycombinator.com

ActorCore - ActorCore Stateful, Scalable, Realtime Backend Framework

read the docs – actorcore.org/introduction...

give us a star – github.com/rivet-gg/act...

ActorCore is on a mission to be the best framework for YOLO coding collaborative & stateful apps. we just added:

📄 prompts.txt
💻 Cursor, Windsurf, & Claude Code integrations
💚 @mintlify.bsky.social hooked us up with auto llms.txt

link below 🧵

GitHub - rivet-gg/actor-core: 🎭 Stateful serverless framework for Rivet, Cloudflare Workers, Bun, and Node.js. Build AI agents, realtime apps, game servers, and more. 🎭 Stateful serverless framework for Rivet, Cloudflare Workers, Bun, and Node.js. Build AI agents, realtime apps, game servers, and more. - rivet-gg/actor-core

read the changelog – actorcore.org/changelog/ov...

get the code – github.com/rivet-gg/act...

ActorCore v0.5.0 changelog

ActorCore v0.5.0 + @hono.dev 🔥

by far our most requested feature: ActorCore now exposes `createRouter` to let you quickly include ActorCore in existing projects

plus: exposed driver API, new topology, and loads of new docs. github & changelog below 🧵

Two days with @anthropic.com Claude Code (vs Aider & Cursor) – currently my favorite copilot.

+ Smart search/replace w/o explicit files
+ Smart auto-architect/ask switching
- No auto-lint/test
- No explicit fs scope (aka /add)
- No web crawling
- Buggy 1.0 UI
- No vim bindings

ActorCore README.md

actorcore.org just passed 300 stars ✨

what do you want to see us ship next? what features do think Durable Objects should include by default?

github.com/rivet-gg/act...

that sounds like a good approach! the only recommendation would be to create a cache or index of "places" since you're going to end up with a lot of fan out requests to locations and choke your system.

we used to just run game servers until recently, so we have a very liberal draining policy on actors if we're upgrading machines (unlike DO which just kills you without warning)

however, if the host node crashes, you're SOL getting that data back

is that a problem?

cheers! we do that for our container solution runtime already. our v8 isolate runtime launched in december, it'd would be an afternoon of work to get the volumes set up correctly 😅

httpfs Extension for HTTP and S3 Support The httpfs extension is an autoloadable extension implementing a file system that allows reading remote/writing remote files. For plain HTTP(S), only file reading is supported. For object storage usin...

it's probably really easy for duckdb. they have a native http/s3 backend. if you can figure out how to wire up fetch correctly in their wasm distribution, you're good to go. duckdb.org/docs/extensi...

mvsqlite has a very similar limitation on foundationdb. fdb has a 10 kb value size limit + a 5s transaction limit, but sqlite doesn't have either of those limitations.

probably works similar to what you have in mind: su3.io/posts/mvsqli...

fun fact: the mvsqlite dev now works at deno

forgot to mention on constraints – it's easy to provide a custom fs driver for the deno runtime (which mocks the node runtime too). but we also have container support (unlike cloudflare), so i'd rather go a level down to FUSE.

in the meantime, we're shipping our sqlite driver with a custom foundationdb vfs backend because remote filesystems aren't going to cut it (yet).

i've only done limited research in to distributed fs, so i'd love any ideas anyone might have.