A transaction management strategy organizes transaction boundaries for a system operation that spans domain modules. Choose among transaction-per-operation, transaction-per-domain-module, and requirements-driven boundaries; collaboration choices affect which strategy fits. section 6.2.4
The named strategies organize boundaries in different ways:
- Transaction-per-operation implements the operation as one ACID transaction; it is the simplest and most common approach in a monolithic architecture. section 6.2.4
- Transaction-per-domain-module and requirements-driven boundaries are alternatives; the latter bases boundaries on operation requirements. section 6.2.4
Creating an order
A single transaction can create an order, reserve credit, and send a confirmation email across Order, Consumer, and Notification Management. A Saga instead sequences transactions; if credit reservation can fail, a compensating transaction can undo earlier updates. If business-rule violations are confined to the first transaction, a simpler Saga can avoid compensation. section 6.2.4
