• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Hibernate over DAO

 
Mahesh Asrani
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All

In our current application we have used the Data Access Object (DAO) j2ee design pattern.

I have been asked to evaluate the use of O/R mapping framework HIBERNATE to replace the traditional DAO approach.

I want to know what are the advantages we derive out of a O/R mapping framework like Hibernate or say
How does Hibernate score over DAO

Kindly give your suggestions

Bye
MA
 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Using Hibernate with DAO is the prudent approach. Then you are not tied in to using Hibernate or whatever other persistance technology you might change to.
 
Pj Murray
Ranch Hand
Posts: 194
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Mahesh Asrani:


I want to know what are the advantages we derive out of a O/R mapping framework like Hibernate or say
How does Hibernate score over DAO



I think you're mixing the technology choice - Hibernate, JDO, EJB CMP - with the design strategy - Data Access Objects.

You can find a comparison of the various data persistence technologies here:

http://www.codefutures.com/weblog/corporate/archives/2005/02/data_persistenc.html

You may also find this blog entry on ORM versus DAO to be interesting.

http://www.codefutures.com/weblog/andygrove/archives/2005/02/data_access_obj.html

Finally, while Hibernate is probably a safe technology choice given the market momentum, it's really a good idea to keep your DAOs so you can upgrade to the new version of Hibernate (with EJB 3.0 persistence)or switch over to something else.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic