Data Access in Fail Tracker

added by Matt_TCF

8/3/2011 6:32:05 PM

139 Views

This is the first in a series of short posts on how data access is handled in Fail Tracker. Future posts will get into how the strategy works with unit testing as well as how advanced topics, such as row-level security, are handled. Read on to find out how Fail Tracker utilizes a simple repository layer around NHibernate for all data access.

Read the full story

1 comments

dpeterson

8/3/2011 6:31:41 PM

I noticed in the repository you implemented that you included a Save method.
It seems like lots of people these days are creating repositories that combine both the repository pattern (http://martinfowler.com/eaaCatalog/repository.html) and the unit-of-work pattern (http://martinfowler.com/eaaCatalog/unitOfWork.html).

Would testing ability be helped or hindered by having greater separation of concerns and splitting the repository you have implemented into separate objects (more strictly following the repository and unit-of-work patterns)?

Thanks for sharing :-)