Senior
Distributed Data Patterns
The transaction you no longer have.
Sagas with compensation, the transactional outbox, idempotent consumers, CQRS, event sourcing, and the two-phase commit you were told about — with the consistency each pattern actually gives you.
0 lessons written3 outlined1 modules~1h reading
After this course you can
- Implement a saga and reason about every partial failure
- Use the outbox pattern so a database write and an event cannot disagree
- Explain CQRS and when the read model is worth the complexity
- Argue for or against event sourcing for a given domain
Curriculum
3 lessons · outlined lessons show their plan01
Distributed transactions and sagasWhy 2PC is avoided, choreography versus orchestration, compensating actions, and the saga that gets stuck halfway.outlinedThe transactional outboxWrite the event in the same transaction as the row, relay it later, and accept at-least-once — then make the consumer idempotent.outlinedCQRS and event sourcingSeparate read models, projections, replay, snapshots, and the operational weight of keeping events forever.outlined