liveBook · Manning

Transaction-per-domain module

As explained in Microservices Patterns, Second Edition

Transaction-per-domain module is a transaction strategy that gives each domain module's work its own transaction.

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

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines the strategy and distinguishes it from operation-based and requirements-driven transaction boundaries.
How it connects
Connects transaction boundaries with collaboration patterns and asynchronous messaging.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.