Convergent/Divergent
summary
If an Ember.js app pushes state to clients it already behaves like a distributed system, and the concrete fix is to embed causality into data structures: explain convergent and commutative replicated data types, contrast state‑based versus op‑based CRDTs, and show the observed-remove set and lattice merges where union/max/OR give associativity commutativity idempotence. The claim is that mathematically proven merge functions let replicas converge without global consensus; implementations include counters, sets, registers and composable maps and they work in practice.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 4:57Building distributed systems
- 9:09Consistency models
- 12:20Consensus challenges
- 17:35Conflict-free replicated data types explained
- 27:20Why CRDTs matter
- 28:44Conclusion
related talks
36mCRDTs Illustrated
45mBuild better apps using CRDTs
32mCRDT and other new ideas for client-server communication
40mDistributed, Eventually Consistent Computations
27mOn the Development of Reactive Systems with Ember.js
52mState management beyond the libraries
29mCRDT: Conflict-free Data Types for Collaborative Editing and Offline-First
36mKnowing What You See - Let's Talk About Front-end Consistency
