CRDTs for Mortals
summary
Argues that local‑first apps are practical by showing a real personal finance app that uses CRDTs, hybrid logical clocks and SQLite on top of a message table as a sync layer. Claims ordering is solved with HLC timestamps and conflicts with last-write-wins maps and grow‑only sets, shows the entire client sync in 630 lines of JavaScript (server 132), an HLC implementation in 256 lines, and reports this simple engine works reliably.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:13Why havent offline first apps taken off
- 1:49Local apps are distributed systems
- 4:16Use cases
- 7:36Clocks
- 10:23Reliability
- 11:27Conflict Resolution
- 12:47CRDT
- 16:08CRDT Implementation
- 18:15Other Features
related talks
24mGoing Local-First: A Primer
40mPractical Demystification of CRDT
18mRethinking Apps with Local-First Architecture
22mHappily Ever After: A CRDT Fairy Tale
39mBuilding a real-time collaboration tool using CRDTs and Kotlin Multiplatform
36mConflict-Free Replicated Datatypes (CRDT)
50mCRDTs in Practice
01h 03mOffline first computing in an online world