Building Microservices Architecture The Right Way based on Saga Pattern
summary
Shows a concrete design: three microservices each with its own database, using the Saga pattern to avoid distributed ACID rollbacks. Demo wiring uses Kafka + MySQL in Docker with an external orchestrator that issues commands, tracks states, and triggers compensation transaction steps on failure. Compares choreography (event chaining, scattered logic) versus orchestration (central coordinator, single point of failure), and demonstrates payment-denied and reservation-exhaustion scenarios plus how the orchestrator resumes when restarted.
AI-written summary · about
chapters (9)
- 0:00Introduction and welcome
- 1:07Microservices data management challenges
- 3:48Why single database is wrong
- 5:56Saga pattern introduction
- 8:56Saga pattern types explained
- 12:11Choreography vs orchestration
- 17:45Demo setup overview
- 18:30Live demo walkthrough
- 22:28Q&A and closing remarks
related talks
35mApplying microservices patterns to a modular monolith
58mImplementing Event-driven Microservices
17mSaga Pattern for Distributed Transactions
51mIntroducing Saga Pattern in Microservices with Spring Statemachine
40mCAPtivating architecture: Navigating Distributed Systems and Microservices
54m3 Patterns for Scalable Microservices
59mGranularity & Communication for Microservice Architectures
24mPatterns of Evolution from Monolith to Microservices