Unit of Work Pattern

Kind: pattern

Layer: Atomic Boundary

Aliases: Unit of Work

Record: architecture:unit-of-work-pattern

Severity: recommended

Scope: application service, persistence

Canonical: Ontology

A design pattern that collects the changes of one use case and commits them together in a single transaction.

Listed in Architecture principles, after Transaction Boundary and before Consistency.

Requires

• Transaction Boundary

Reinforces

• Atomicity
• Consistency

Enables

• Coordinated Persistence

Conflicts with

• Scattered Save Calls

In tension with

• Repository Complexity

Tensions

• Unit of Work Pattern / Repository Complexity

Violated by

• Scattered Save Calls

Severity

• recommended

Category

• Transactions / State / Concurrency

Linked from

• Node design
• Transactions / State / Concurrency
• Transactions / State / Concurrency
• Severity levels
• The resolutions