Unit of work

A unit of work ( UoW for short ) is a behavioral pattern in software development.

“A Unit of Work keeps track of everything you do during a business transaction that can affect the database. When you're done, it figures out everything that needs to be done to alter the database as a result of your work. "

- Martin Fowler

A UoW encapsulates one or more repositories and a list of actions to be carried out which are necessary for the successful implementation of a self-contained and consistent data change. A UoW is also responsible for handling concurrency issues, which it can use transactions and stability patterns to do .

Individual evidence

^ ^A ^b ^c Martin Fowler: Patterns of Enterprise Application Architecture . Addison-Wesley-Longman, Amsterdam 2002, ISBN 0-321-12742-0 .
^ ^A ^b ^c Martin Fowler: Unit of Work. Accessed March 8, 2018 .
↑ ^a ^b ^c Unit of Work. In: Portland Pattern Repository. Accessed March 8, 2018 .
↑ Michael T. Nygard: Release It! Design and Deploy Production-Ready Software . O'Reilly, 2007, ISBN 978-0-9787392-1-8 (English, 326 pages).

[PoEAA-1] A ^b ^c Martin Fowler: Patterns of Enterprise Application Architecture . Addison-Wesley-Longman, Amsterdam 2002, ISBN 0-321-12742-0 .

[fowler-2] A ^b ^c Martin Fowler: Unit of Work. Accessed March 8, 2018 .

[c2-3] Unit of Work. In: Portland Pattern Repository. Accessed March 8, 2018 .

[releaseit-4] Michael T. Nygard: Release It! Design and Deploy Production-Ready Software . O'Reilly, 2007, ISBN 978-0-9787392-1-8 (English, 326 pages).