Persisting Object Oriented State in Functional Programming
summary
Concrete claim: a BEAM-backed database layer makes object-style, named state persistent and distributable. Implementation details include a persisted gen_server wrapper that calls get/put on every state change, a zookeeper-based registry for unique process names, and per-object Lamport timestamps instead of vector clocks. Examples and analogs: Orleans/ Halo, Akka, couchdb/pouchdb sync, Service Fabric. Real-world scale: Wunderlist architecture spawns about 80 small services and an offline-first model that actually works.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:00PERSISTING STATE
- 7:09TASKS IS ACTUALLY
- 10:42AKKA & WEBSOCKETS
- 12:08OBJECT STATE
- 17:11ORLEANS
- 25:26TIC TAC TOE
related talks
35mPersisting Relations Across Time and Space
28mStateful Applications in the Age of Durable Execution
50mOrthogonal Persistence, the Model
26mIdentity in a World of Values
29mFunctional Programming & NoSQL Design
29mManaging State in Apache Flink
40mPutting off Persistence
51mExploring Stateful Microservices in the Cloud Native World