Orthogonal Persistence, the Model
summary
Argues persisting running processes (not just data) is practical and transformative: domains with versioning, erasure coding across five global backups, end-to-end encryption with one‑time pads, and system‑level policies for publish/share. Claims transactions are the wrong API and that critical sections plus memory barriers are the two language primitives needed; marshaling code drops by 30–70% and productivity doubles. Lots of systems design, a semiformal model and research pointers but no polished consumer demo yet.
AI-written summary · about
chapters (9)
- 0:00Introduction to persistence
- 2:13The case for persistence
- 7:59Problems with current systems
- 13:33User-focused persistence
- 19:14Persistence for developers
- 27:31Critique of current models
- 33:16New programming models
- 39:08System-wide decoupling
- 44:21Conclusion and future impact
related talks
33mPersisting Object Oriented State in Functional Programming
55mPolyglot Persistence with Java
17mPreview: Persistent Memory
32mPeristence as the Single Source of Truth
27mNetworking & Persistence in Mobile Applications at Scale
44mPolyglot Data
35mPersisting Relations Across Time and Space
32mPolyglot Persistence