Transaction Boundary

Kind: constraint

Layer: Atomic Boundary

Record: architecture:transaction-boundary

Severity: mandatory

Scope: unit of work, aggregate, service

Canonical: Ontology

A rule or precondition that a transaction covers exactly the writes of one unit of work inside one service.

Listed in Architecture principles, after ACID and before Unit of Work Pattern.

Requires

• Consistency Rules

Reinforces

• Atomicity
• Unit of Work Pattern

Enables

• Safe State Mutation

Conflicts with

• Hidden Distributed Transaction

In tension with

• Large Transaction Scope

Tensions

• Transaction Boundary / Large Transaction Scope

Contracts

• Transaction Boundary

Violated by

• Hidden Distributed Transaction

Refactored by

• Restrict Exports
• Saga Pattern

Severity

• mandatory

Category

• Transactions / State / Concurrency

Linked from

• Separate, trade, or mitigate
• The principle architecture
• Architectural rules and principles
• Transactions / State / Concurrency
• Core Modular Design
• Transactions / State / Concurrency
• Architecture
• Severity levels
• The resolutions