Master the IT-English vocabulary of distributed transactions: the saga pattern, compensating actions, orchestration vs choreography and eventual consistency.
0 / 5 completed
1 / 5
Why is a single ACID transaction hard across microservices?
With a database-per-service, you can't span one ACID transaction across services, so patterns like saga are used.
2 / 5
In the 'saga pattern', a multi-step operation is modelled as what?
A saga is a series of local transactions across services, coordinated to achieve an overall outcome.
3 / 5
If a saga step fails, a 'compensating action' is run. What does it do?
Compensating actions roll back earlier steps' effects (e.g. refund a charge) since there's no global rollback.
4 / 5
What distinguishes 'orchestration' from 'choreography' in sagas?
Orchestration centralises control in a coordinator; choreography is decentralised via event reactions.
5 / 5
Which sentence correctly uses 'eventual consistency' for sagas?
Sagas trade immediate consistency for eventual consistency, with the system converging once steps finish.