CRDT: Conflict-free Data Types for Collaborative Editing and Offline-First
summary
Shows how CRDTs power collaborative editors with a concrete implementation: actions-as-ops sent over websockets, Atom Teletype style merging, and Redis CRDT support as real-world deployments. Describes an optimistic multi‑master model that records per‑character actions, preserves causal order via timestamps/indexes between letters, replays and undoes changes, and syncs after long offline periods (subway/poor networks). Demonstrates working prototypes and argues offline‑first improves UI latency and conflict resilience.
AI-written summary · about
chapters (7)
- 0:00Introduction and setup
- 7:48What are CRDTs
- 13:03How CRDTs solve conflicts
- 18:52Practical examples of CRDTs
- 24:12Offline-first and scalability
- 27:43Performance and trade-offs
- 28:46Summary and Q&A
related talks
32mCRDT and other new ideas for client-server communication
13mHow to make a real-time collaborative text editor in 5 easy steps!
45mBuild better apps using CRDTs
49mWhat CRDTs, distributed editing and the speed of light means to your writer friends
36mCRDTs Illustrated
40mNew algorithms for collaborative text editing
37mBuilding a Collaborative Text Editor
34mUsing CRDTs Beyond Text Editors