Saga Pattern
In plain terms
Managing distributed transactions as a sequence of local steps.
Going deeper
A saga coordinates a multi-service transaction through local transactions, with compensating actions to undo on failure, avoiding distributed locks. It keeps data eventually consistent.
Under the hood
Orchestration or choreography drives the steps; compensation replaces rollback in distributed systems.
Examples
Microservice transactions, order processing, eventual consistency, compensation.
Think of it like...
Like a multi-leg trip where, if one booking fails, you cancel the others to undo the journey.