Case studies / 2 / 2
Case: Figma multiplayer editing
Several people edit one design file at once. How Figma keeps everyone in sync without operational transforms: a server that is the single authority, last-writer-wins per property, hidden echoes, client-made ids, cycle checks and fractional indexing. Source: https://www.figma.com/blog/how-figmas-multiplayer-technology-works/
- 14 min
- Advanced
- 12 steps
- Unacknowledged
- 0
- Flickers
- 0
- Lost edits
- 0
- request
- reply
- redelivery
- duplicate
- lost
Numbers are a model scenario, not measurements
The real request
Alice's browser → Document processRequest
open a file (simplified)
1) download a full copy of the document1
2) open a WebSocket to the process that serves this document2
3) from now on only changes travel, in both directions3
full copy— The starting state. Changes are applied on top of it.WebSocket— A long-lived connection to the process that owns this document.only changes— Small messages instead of the whole file each time.
Build it yourselfCheat sheetCompare lessons
Course: 74 lessons
01 Foundations
02 Scaling
03 Data & storage
04 Communication
05 Reliability
06 Architecture
07 Security
08 Shipping
09 Whole systems
10 Business processes
11 Case studies