Epic Programming: How We Write Clear, Maintainable Sagas
summary
The talk explains using the Saga pattern to implement coordinated, consistent changes across multiple microservices. It covers practical approaches for writing clear, maintainable sagas for distributed transactions in high-load systems.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:48Choreography vs orchestration
- 3:12Why orchestration
- 6:23Saga components in Go
- 9:34Flat structure problems
- 11:41Structured code vs text
- 13:24Panic for critical errors
- 16:13Point of no return
- 18:39Handling impossible cases
- 20:46Debugging distributed systems
- 22:51Saga for GET requests
- 23:33Async APIs via sagas
- 24:36Why not existing tools
- 26:45Q&A part 1
- 28:12Q&A part 2
- 30:40Parallel steps and compensation
- 32:43Orchestrator state persistence
- 33:25DSL for sagas future
- 34:52Chat Q&A part 1
- 35:59Chat Q&A part 2
- 37:28Saga maintenance
related talks
38mEpic programming: how we write clear and maintainable sagas
17mSaga Pattern for Distributed Transactions
55mTackling transactions in Microservices applications
51mIntroducing Saga Pattern in Microservices with Spring Statemachine
27mBuilding Microservices Architecture The Right Way based on Saga Pattern
47mSaga Pattern Made Easy
59mGranularity & Communication for Microservice Architectures
50mTransactional solutions for microservices