Unit of work

● Article ● Talk ● Language ● Watch ● Edit

Aunit of work^[1] is a behavioral patterninsoftware development. Martin Fowler has defined it as everything one does during a business transaction which can affect the database.^[2] When the unit of work is finished, it will provide everything that needs to be done to change the database as a result of the work.^[2]

A unit of work encapsulates one or more code repositories^[de] and a list of actions to be performed which are necessary for the successful implementation of self-contained and consistent data change. A unit of work is also responsible for handling concurrency issues,^[3]^[4] and can be used for transactions^[3]^[4] and stability patterns.^{[de]^[5]}

References

^ Martin Fowler. Patterns of Enterprise Application Architecture. ISBN 0-321-12742-0.

^ ^a ^b Martin Fowler (2002), Patterns of Enterprise Application Architecture, Amsterdam: Addison-Wesley-Longman, ISBN 0-321-12742-0

^ ^a ^b Martin Fowler. "Unit of Work". Retrieved 2018-03-08.

^ ^a ^b "Unit of Work". Portland Pattern Repository. Retrieved 2018-03-08.

^ Michael T. Nygard (2007), Release It! Design and Deploy Production-Ready Software, O’Reilly, ISBN 978-0-9787392-1-8

Retrieved from "https://en.wikipedia.org/w/index.php?title=Unit_of_work&oldid=1219188501" Last edited on 16 April 2024, at 07:30

●This page was last edited on 16 April 2024, at 07:30 (UTC). ●Content is available under CC BY-SA 4.0 unless otherwise noted. ●Privacy policy ●About Wikipedia ●Disclaimers ●Contact Wikipedia ●Code of Conduct ●Developers ●Statistics ●Cookie statement ●Terms of Use ●Desktop