CRDT and other new ideas for client-server communication
summary
Argues that CRDTs plus action-based replication over WebSocket two-way sync solve real collaborative-edit headaches: uses Redux-style actions as the unit of change, Lamport/vector timestamps and unique client IDs to order ops, and special “undo” actions when the server rejects a change. Demonstrates an optimistic UI that applies edits immediately, queues offline actions and later reconciles them; reports this approach runs in a working task manager and survives dropped or reordered packets.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:50Next big project search
- 3:58Revolutionary ideas evolution
- 6:05Collaborative task manager
- 7:58Distributed systems and CRDTs
- 9:22Concurrent edits with CRDTs
- 11:15State management with CRDTs
- 13:40Optimistic UI and offline
- 15:52Undo and illegal ops
- 17:21Action ordering in systems
- 19:30Logical clocks over real time
- 20:56Conflict resolution in fields
- 22:05CRDTs and their properties
- 23:35Text editing with CRDTs
- 25:19CRDT architecture
- 26:44Out-of-order actions handling
- 27:51CRDTs for unreliable internet
- 29:36Optimistic CRDT design
- 30:40CRDTs performance and UX
- 31:26Conclusion and future
related talks
29mCRDT: Conflict-free Data Types for Collaborative Editing and Offline-First
23mBuilding Offline and Real-Time Applications - The Magic of CRDTs
45mBuild better apps using CRDTs
22mHappily Ever After: A CRDT Fairy Tale
13mHow to make a real-time collaborative text editor in 5 easy steps!
49mWhat CRDTs, distributed editing and the speed of light means to your writer friends
33mDoes the network seem thin up here? Collaborating with mountaintop mesh networks
37mBuilding a Collaborative Text Editor