Turning the database inside out with Apache Samza
summary
Claim: turn the database inside out by making the immutable commit log the primary data model and building materialized views from it. Implementation uses Apache Kafka as a distributed durable log and Apache Samza to stream-process and maintain per-partition local state. Result: fully precomputed caches (no cold starts), simpler, sequential update semantics, better scalability and recoverability. Tradeoffs: views update asynchronously so clients see eventual consistency; idempotence and transactional layers are needed for exact once semantics.
AI-written summary · about
chapters (10)
- 0:00Database architecture shift
- 3:55Shared mutable state problems
- 7:50Immutability in replication logs
- 11:05Flaws in app caching
- 14:19Materialized views limitations
- 17:49Four forms of derived data
- 20:59Turning databases inside out
- 25:12Log-centric architecture benefits
- 29:46Streams in app design
- 35:43Q&A
related talks
43mBack to fundamentals: from databases to event-driven platforms
34mChasing the Stream Processing Utopia
20mWrites, 3 ways: Postgres, Apache Kafka® and Apache Iceberg™
48mUnlocking Real-time Insights: Enhancing Your Databases With Stream Processing
33mThe rise and fall of the full stack database
44mHow to Manage State in Apache Kafka
17mOvercome By Events - Apache Kafka And Event-oriented Architecture
39mModern Event-driven Architecture: Adopting Data in Motion
