Tags » Unit Of Work

Repository Implementations

In my previous post I have presented a way to separate your data access from the business logic, when a relational database is used. I have shown another implementation of the well-known… 1,769 more words


Separating Data Access Concern

In our days most of the applications that have a relational database as storage, use an ORM to access the data. The ORM (Entity Framework, Hibernate, etc.) does most of the data access implementation. 2,131 more words


Unit of Work, Repository, Entity Framework, and Persistence Ignorance

Let me lay my cards on the table. I’m not an expert on design patterns. But I’ve read some books, some blog posts, and followed many a debate online. 1,927 more words


Repository + Unit Of Work Pattern Demystified

The repository and unit of work patterns are intended to create an abstraction layer between the data access layer and the business logic layer of an application. 1,800 more words

Design Pattern

Creating a sample WinForms application, part three: abstract Xpo business class objects

In part two of this series we learned how to create a data layer which tells Xpo how to connect to our data store (in this case, a Sql Express server located on the same machine). 1,098 more words


Unit Of Work

Note There are many ways to implement the repository and unit of work patterns. You can use repository classes with or without a unit of work class. 118 more words