Transaction-per-domain module gives each domain module’s work its own transaction, organizing transaction boundaries around architectural modules rather than whole operations or operation-specific requirements. section 6.2.4
Choose among three transaction-boundary strategies:
- Transaction-per-operation uses one transaction for a system operation. section 6.2.4
- Transaction-per-domain module organizes transactions around domain modules. section 6.2.4
- Requirements-driven boundaries shape transaction management around the operation’s requirements. section 6.2.4
