Safe Passage: Messaging in a distributed systems environment
summary
Explains why distributed message delivery fails in predictable ways and which fixes actually work: use an event log (push or pull) to close the non‑transactional gap, treat Kafka as an at‑least‑once transport with idempotent handling, and move toward event sourcing and CQRS so services can own schemas and replicate necessary views. Demonstrates tradeoffs (lost vs duplicated messages, eventual consistency), cites Netflix’s chaos-testing mindset and practical claims about what guarantees are realistic.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:13The Monolith
- 14:48Microservice System
- 19:01Independent eventually consistent transactions
- 26:59Message Propagation-Push versus Pull
- 30:10Event Sourcing and CQRS
- 36:48Reliable Data Replication
- 42:11Annual Size of the Global Datasphere
- 42:50Reactive Systems & Reactive Programming
related talks
56mFrom Unreliable to Resilient: Mastering Distributed Systems
51mComplex Event Flows in Distributed Systems
34mAtomicity and Consistency Across Databases and Messaging Systems
45mDo Distributed Systems they said. It'll be fun they said.
30mDo Distributed Systems, they said. It'll be fun, they said
17mEnsuring Reliable Distributed Transactions in Logistics
02h 42m!!! Do not publish or share !!!!
44mFrom Synchronous to Asynchronous Distributed Microservices