Comments on: Repeat After Me: Repositories Aren’t DAOs

By: Domain-Driven Bolovo, Passando Conhecimento e etc. « Fragmental

Domain-Driven Bolovo, Passando Conhecimento e etc. « Fragmental — Mon, 18 Jan 2010 11:35:58 +0000

[…] http://fragmental.tw/2008/04/25/repeat-after-me-repositories-arent-daos/ […]

By: Sławek S.

Sławek S. — Wed, 29 Oct 2008 22:03:20 +0000

You write about “business concept” of Repository in previous post…

Could You explain it to me as if I were and idiot what is the difference between:
- classic DAO but just called Repository (ex OrdersRepository instead of OrdersDAO)
- your real Repository

I think that code example would be sufficient - interface and impl for both cases. If You could also add some kind of philosophyical explanation to examples than everything should be clear. But I think that only example can clarify this issue.

By: Rafael Ponte

Rafael Ponte — Mon, 05 May 2008 14:18:31 +0000

Between all patterns from the DDD the Repository is what brings more confusion for developers, maybe because they think always in DAOs when if speak about persistence!

By: Daniel Aragao

Daniel Aragao — Tue, 29 Apr 2008 14:18:53 +0000

The industry seems to be leaning towards accepting this misuse as a default.
e.g. this is Spring’s 2.5 @Repository annotation doco:
“public @interface RepositoryIndicates that an annotated class is a “Repository” (or “DAO”).”
Cheers.