Part 1 of 8 · 1 min read
Why this page comes eighth in Level 13
In this module you will
- Scope a real-time editor and size its traffic and storage.
- Explain why simultaneous edits conflict, and why locking is too slow.
- Describe operational transformation (OT) with a worked example.
- Describe a CRDT for text and compare it with OT.
- Draw the architecture: sessions, a per-document server, a log, snapshots, presence and offline use.
This case turns the replication ideas of Level 5 into a product. Each user's screen is a replica of the document, and edits flow between replicas. It needs multi-leader thinking (conflicts, merging), WebSockets (page 1), a log with snapshots (pages 7 and 9) and per-document ownership. The main source is "Designing Data-Intensive Applications" by Martin Kleppmann (the sections on collaborative editing and automatic conflict resolution). Numbers marked "made up" only show the idea.