How Notion rebuilt its editor around CRDTs to end concurrent-edit data loss
blaizedsouza · x · 2026-09-19
Notion engineers detail their 2025 collaborative editing overhaul. Previously the editor used last-write-wins per block: concurrent edits to the same block silently overwrote each other, and the planned Offline Mode would have made data loss far worse.
The team rebuilt the underlying system and data model with a CRDT-based conflict-free rich-text editing system, plus techniques to handle Notion's unique block-based document model, so hundreds or thousands of collaborators can edit concurrently with proper merging.
Related event: Notion Rebuilds Editor with CRDT for Real-Time Collaboration(2 posts)→
More from coding & agent
- Power user burns 1bn tokens a day at 98.65% cache hits, weighing GLM-5.3 vs DeepSeek after Claude Code weekly limits — julianharris · 2026-09-19
- Two MCP orchestration patterns: Jev as LLM tool orchestrator vs LLM as a tool — blaizedsouza · 2026-09-19
- Jev controls Ableton Live by voice, ~40x faster than LLM computer use — jordiponsdotme · 2026-09-19
- Dev wires up a vLLM reproduction in minutes with Codex, runs it on DGX Spark — remilouf · 2026-09-19
- Dev builds Vercel-like tool to turn any project into a hosted MCP server with one prompt — Corridl · 2026-09-19
- Querit launches coding-focused search built for code agents and IDEs — SucceededMind · 2026-09-19