In using the Repository design pattern, you can hide the details of how the data is eventually stored or retrieved to and from the data store. This data store can be a database, an xml file, etc.

In many cases the repository pattern is an apparently unnecessary layer around the underlying data access technology. But once you have a repository in place, many new opportunities become available.

We examined the repository design pattern in an earlier article here. In this article, we’ll explore the unit of work design pattern with relevant code examples to illustrate the concepts covered.