Repository Pattern versus DAO Pattern

Hi,

First of all, great job with DoFactory's Design Pattern Framework. In the recent version 4.0 the Repository Pattern was included.
Now I am trying to understand the difference between the Repository Pattern and the DAO (Data Access Object) Pattern.

I have read the "official" definition from Fowler and Googled some additional information, but I guess I need a "for dummys" explanation, I hope someone can help me see the real difference between these two pattern and when is it convenient to apply one or the other.

Perhaps if someone can give me an example of a Repository Pattern that is not a DAO, or a DAO implementation that is not a Repository I can have a better understanding.

Thanks.

Maximiliano Aguilera Adasme, Jul 29, 2010

Reply 1

Thank you very much for those links :)

Very useful.

Maximiliano Aguilera Adasme, Aug 09, 2010

Reply 2

Hi,

Just a suggestion.

Search out Domain Driven Design (DDD).

The Repository is the kind of the foundation for DDD.

You can use this at various levels of the application.

Some Suggested links from muy bookmarks...
http://www.codeinsanity.com/2008/08/repository-pattern.html

http://blog.fedecarg.com/2009/03/15/domain-driven-design-the-repository/

http://devlicio.us/blogs/casey/archive/2009/02/20/ddd-the-repository-pattern.aspx

http://en.wikipedia.org/wiki/Domain-driven_design

http://msdn.microsoft.com/en-us/magazine/dd419654.aspx

Ronald Garlit, Aug 08, 2010