DotNetKicks.com : Stories kicked by rao.ritesh

The Unit of Work Pattern - Part Deux

Thu, 09 Oct 2008 22:48:58 GMT

Last week's post, Implementing a persistence ignorant Unit of Work framework (if you haven't read this post yet I would encourage you to do so as this post builds on the previous post), showed how to implement a foundation for the Unit of Work pattern that can be used to implement specific Unit of Work components for any type of persistence framework. In this post I'm going to enhance on the existing foundation to add another level to the Unit of Work, something I call the Unit of Work Scope that allows cascading unit of work scopes and transaction sharing.

Implementing a persistence ignorant Unit of Work framework

Thu, 09 Oct 2008 22:48:22 GMT

In the previous post; The Unit of Work Pattern I put down some thoughts on the Unit of Work pattern. In this post I delve into implementing a Unit of Work framework that allows persistence ignorance and provides a base for a unit of work component that I can use in Rhinestone.

The Unit of Work Pattern

Sun, 28 Sep 2008 07:02:48 GMT

Discussion and examples on the Unit of Work pattern.

Building a generic IoC wrapper.

Wed, 27 Aug 2008 23:29:48 GMT

This post steps through the process of creating an IoC wrapper that allows your application to be decoupled from the choice of IoC container. Using the IoC wrapper you can swap out IoC containers without affecting your application code and having to update code / references.

Persistence Ignorance and DDD with RepositoryBase

Wed, 20 Aug 2008 00:46:32 GMT

This post goes into developing a sample that uses the repository base implemented in my previous post, RepositoryBase. The post also shows how you can leverage RepositoryBase and achieve a degree of Persistence Ignorance by implementing two separate persistence layers using Linq to SQL and NHibernate and transparently swapping one out for the other without affecting your domain or tests.

Implementing a Repository and Specificaiton pattern using Linq

Fri, 15 Aug 2008 20:31:03 GMT

In my previous post I put down some thoughts on the Repository and Specification patterns and in the end said that with the introduction of Linq and the growing popularity of ORM frameworks and their support for Linq, it's time to look back at these two patterns and see how we can leverage Linq to simplify the patterns and make them infrastructure agnostic.