Wikitopia
Unit of Work Pattern
conceptDesign Pattern
Try in Playground →
Overview
Use casemaintaining a list of objects affected by a business transaction and coordinates writing out changes and resolving concurrency problems
Knowledge graph stats
Claims13
Avg confidence94%
Avg freshness99%
Last updatedUpdated 5 days ago
Trust distribution
100% unverified
Governance
Not assessed
Contribute governance data →

Unit of Work Pattern

concept

Maintains list of objects affected by business transaction and coordinates writing changes to database

Compare with...

documented in

ValueTrustConfidenceFreshnessSources
Patterns of Enterprise Application Architecture○UnverifiedHighFresh1

publication year

ValueTrustConfidenceFreshnessSources
2002○UnverifiedHighFresh1

primary use case

ValueTrustConfidenceFreshnessSources
maintaining a list of objects affected by a business transaction and coordinates writing out changes and resolving concurrency problems○UnverifiedHighFresh1

category

ValueTrustConfidenceFreshnessSources
Enterprise Application Architecture Pattern○UnverifiedHighFresh1

implemented in framework

ValueTrustConfidenceFreshnessSources
Entity Framework○UnverifiedHighFresh1
Hibernate○UnverifiedHighFresh1

solves problem

ValueTrustConfidenceFreshnessSources
object change tracking in business transactions○UnverifiedHighFresh1

described by

ValueTrustConfidenceFreshnessSources
Martin Fowler○UnverifiedHighFresh1

addresses concern

ValueTrustConfidenceFreshnessSources
transaction management○UnverifiedHighFresh1
database concurrency control○UnverifiedHighFresh1

pattern type

ValueTrustConfidenceFreshnessSources
Data Source Architectural Pattern○UnverifiedHighFresh1

commonly used with

ValueTrustConfidenceFreshnessSources
Data Mapper Pattern○UnverifiedHighFresh1
Identity Map Pattern○UnverifiedModerateFresh1

Related entities

Claim count: 13Last updated: 4/5/2026Edit history