Post

We evaluated a lot of frameworks (this was back 2-3 years ago so keep that in mind). As you can tell from our blog, yjs did not cut it for us.

We ended up building a centralized stateful service that optimistically writes with a transaction log. Thats it. Nothing algorithmically fancy. Boring systems stuff.

15/11/25, 6:33 am0 reposts1 like

reboot.devReboot | Reactive Backends, Durable MCPReboot is a React's bullet-proof backend. With Reboot, you build reactive backends out of durable data structures that safely compose into scalable distributed systems.

We did start with durable objects but ended up partnering with reboot.dev and been satisfied. Performance is great and reboot clients handles the reactivity and idempotency for us.

github.comGitHub - nytimes/react-prosemirror: A library for safely integrating ProseMirror and React.A library for safely integrating ProseMirror and React. - nytimes/react-prosemirror

We use github.com/nytimes/reac... for our render layer vs tiptap as we think working prosemirror transitions gave us better correctness and performance.

Tiptap works great for single player or if you don’t expect to have a lot of conflicts. It’s the only solution out there if you want comments out of the box as well. We do expect to have conflicts and have many people to touch Moment docs, so this is the solution we went with that works for us.

Again this is how we did it and I’m sure there are better ways. But this works for us in terms of correctness (and ensuring no data is lost on conflict), performance and operations.