Comments on: Repository or DAO? http://warren.mayocchi.com/2006/07/27/repository-or-dao/ Life, Software Development, Creativity: What I care to write about Thu, 27 Oct 2011 21:33:17 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: JAOO Brisbane: Goldilocks and the Concurrent Processes at A Few More Words http://warren.mayocchi.com/2006/07/27/repository-or-dao/comment-page-1/#comment-2717 JAOO Brisbane: Goldilocks and the Concurrent Processes at A Few More Words Thu, 29 May 2008 10:44:47 +0000 http://www.mayocchi.com/blog/2006/07/27/repository-or-dao/#comment-2717 <p>[...] complexity. Getting your design just right is a primarily a craft. It may be helped by things like Domain Driven Design or reducing irreversible architecture choices by removing them or delaying them. Software [...]</p> [...] complexity. Getting your design just right is a primarily a craft. It may be helped by things like Domain Driven Design or reducing irreversible architecture choices by removing them or delaying them. Software [...]

]]> By: Koert http://warren.mayocchi.com/2006/07/27/repository-or-dao/comment-page-1/#comment-776 Koert Wed, 09 May 2007 12:02:19 +0000 http://www.mayocchi.com/blog/2006/07/27/repository-or-dao/#comment-776 <p>I think the comment "including business representatives to whom DAO would need constant explanation" is the most compelling reason to use Repository instead of DAO. Otherwise, I see little difference between them.</p> <p>You could just use Hibernate directly in the Repository, since it provides an abstraction to the persistence anyway. I think it's theoretically a good idea to layer the persistence in a DAO layer so you can replace it easily, but it requires more work and costs.</p> <p>I would prefer to use Location as parameter to find: find(Location location).</p> I think the comment “including business representatives to whom DAO would need constant explanation” is the most compelling reason to use Repository instead of DAO. Otherwise, I see little difference between them.

You could just use Hibernate directly in the Repository, since it provides an abstraction to the persistence anyway. I think it’s theoretically a good idea to layer the persistence in a DAO layer so you can replace it easily, but it requires more work and costs.

I would prefer to use Location as parameter to find: find(Location location).

]]>