- Vitess Distributed Database Best Practices
Community-derived best practices for Vitess MySQL sharding, covering cross-shard transactions, CDC and the outbox pattern, distributed transaction patterns, and deployment.
- Saga Choreography
Describes the Saga Choreography pattern, which keeps data consistent across services through event subscriptions instead of a central coordinator, with an AWS order-flow example.
- Saga Orchestration
Describes the Saga Orchestration pattern, which uses a central orchestrator such as AWS Step Functions to coordinate distributed transactions and compensating actions.
- Transactional Outbox
Describes the Transactional Outbox pattern, which solves the dual-write problem by saving events in the same transaction as the data, using an outbox table or change data capture.
- Compensating Transaction Pattern
Explains how to undo the steps of an eventually consistent, multi-step operation by running compensating actions instead of a traditional ACID rollback, with a travel-booking example.
- Saga Pattern
Keep data consistent across microservices with a sequence of local transactions and compensating transactions, using choreography or orchestration instead of two-phase commit.
- Scheduler Agent Supervisor Pattern
Coordinate a set of distributed actions as a single operation, with a scheduler, agents, and a supervisor that recovers or compensates failed steps.
- Retry And Circuit Breaker
Covers retry with gradual backoff, the Circuit Breaker pattern, distributed transaction techniques such as SAGA, and the Outbox pattern for reliable messaging.