3 Patterns for Scalable Microservices
summary
Explains three patterns for keeping microservices scalable and consistent without distributed transactions: the Outbox Pattern, the View (read-model) Database Pattern, and the SAGA Pattern. Describes storing events in Kafka and service-local databases via the outbox, then either populating other services’ view databases or coordinating distributed writes with SAGA, and outlines practical implementation details and pitfalls.
AI-written summary · about
chapters (7)
- 0:00Microservices introduction
- 7:25Microservices ground rules
- 10:58Database per service
- 15:40Outbox pattern
- 23:53Saga pattern for consistency
- 41:09Demo: Saga orchestration
- 51:10Conclusion
related talks
27mBuilding Microservices Architecture The Right Way based on Saga Pattern
53mEffective Microservice Communication and Conversation Patterns
47mEvent-Driven Microservices = Microservices Done Right
24mPatterns of Evolution from Monolith to Microservices
51mPatterns & Practices of Implementing Event-driven MicroSvc...
01h 07mChallenges of microservices Distribution Systems
47mThe Rise of Reactive Microservices
27mHow Micro-Service Patterns Change When the Database Scalable