Safe Passage: Messaging in Microservice Environments
summary
Describes concrete messaging choices: use consumer pull into an event log so producers only append and consumers recover offsets, avoiding non‑transactional gaps when writing a DB then pushing to Kafka or Pulsar. Classifies delivery as at-most-once, at-least-once and the illusion of exactly‑once, explains duplicate handling, and shows patterns that replicate customer views locally to remove cross‑service calls. Discusses practical failures—network, partial crashes, lost responses—and recommends designing for retries, idempotency and chaos testing.
AI-written summary · about
chapters (9)
- 0:00Start
- 5:37The Monolith
- 10:54strong cohesion on the inside
- 13:45The 2002 Amazon API mandate...
- 15:17Microservice System
- 19:16Independent eventually consistent transactions
- 22:35Say goodbye to
- 29:34Message Propagation - Push versus Pull
- 31:39Event Sourcing and CQRS
related talks
27mApplication Integration Patterns for Microservices
11mLightning Talk: Event Based Communication in Complex Micro-service...
01h 03mBeyond Pub/Sub - Advanced Messaging Patterns
59mEffective Microservice Communication and Conversation Patterns
01h 01mBeyond Pub/Sub - Advanced Messaging Patterns
37mBeyond Microservices: Streams, State & Scalability
53mMessaging: The fine line between awesome and awful
01h 11mEmbracing Messaging and Eventual Consistency in your Microservices Solutions