Unit of Work design pattern
For a new project at work I came along this design pattern. On the web I found some interesting posts about this one I really like to share with you.
The Unit of Work design pattern solves the problem, that other components / layers in your software then the persistency layer needs to keep track on which data needs to be inserted, updated or deleted. Also this pattern makes sure that all the data is saved within one transaction.
- The Unit of Work Pattern:
http://www.codeinsanity.com/2008/09/unit-of-work-pattern.html - Implementing a persistence ignorant Unit of Work framework:
http://www.codeinsanity.com/2008/10/implementing-persistence-ignorant-unit.html - Confusing unit-of-work with threads:
http://www.infoq.com/news/2007/09/confusing_uow_with_threads