EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Lobsters·22d ago·5 min read
How Notion handles concurrent editing with CRDTs
TL;DR
Notion redesigned its text editing system to support concurrent editing using Conflict-free Replicated Data Types (CRDTs), enhancing collaboration among users. This change prevents data loss during simultaneous edits, making teamwork more efficient.
✦ Why It Matters
Evaluate your current collaborative tools and consider adopting CRDTs for better concurrent editing.
Key Takeaways
- Implement CRDTs for conflict-free editing
- Avoid last write wins systems in collaborative tools
- Store edits in separate records to minimize data loss
- Support offline editing without losing changes
Full Summary
Notion's collaborative editing capabilities were limited until 2025, primarily due to a 'last write wins' (LWW) approach that led to data loss when multiple users edited the same block. To address this, Notion implemented Conflict-free Replicated Data Types (CRDTs), which allow for conflict-free rich-text editing.
This system enables users to make concurrent edits without overwriting each other's changes, even when working offline. By storing each block as a separate database record, Notion minimizes the risk of data loss and enhances the overall user experience.
The redesign not only improves collaboration but also supports unique cases within Notion's document model, allowing teams to work more seamlessly together.