126: James Long - Building Distributed Local-First JavaScript Applications

What It Covers

James Long explains building Actual, a local-first budgeting app using CRDTs for offline-first sync without central database, leveraging SQLite, Electron, and distributed systems concepts from backend architecture applied to client applications.

Key Questions Answered

• •CRDT Architecture: Conflict-free replicated data types enable true offline apps by duplicating data twice—normalized SQLite tables for queries and a messages table with hybrid logical clocks that replay in consistent order across all devices without conflicts.
• •Merkle Tree Syncing: Sync protocol uses Merkle trees to hash message chunks hierarchically, comparing single root hashes between clients to identify divergence points, then walking down tree branches to find exact messages needing sync without transferring entire databases.
• •Eventual Consistency Trade-offs: Apps must handle temporarily inconsistent data by normalizing database structure maximally, never deleting records (only tombstone flags), and querying only fully-consistent data at read time to prevent foreign key references to nonexistent records during sync.
• •Security Considerations: Electron apps allow JavaScript modification by unpacking and repacking, creating phishing risks for sensitive data like banking credentials. Service workers in browsers provide better security guarantees through sandboxing, making web-based local-first apps potentially more secure.
• •Service Worker Backend: Web implementation would run entire backend logic in service worker with IndexedDB for messages and WebAssembly-compiled SQLite in memory, enabling multiple browser tabs to sync instantly through single background process while maintaining offline functionality.