Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

hibernate vs. OJB

 
Morgan Christian
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Howdy all! Long time lurker!

Anyhow we are evaluating a data abstraction layer... I've got limited experience with hibernate (and was impressed), however I just learned about OJB...

Thoughts? Pros/Cons?

Thanks!
 
Pj Murray
Ranch Hand
Posts: 194
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If you're looking for pros and cons of persistence technologies, you may find this interesting:

http://www.codefutures.com/weblog/corporate/archives/2005/02/data_persistenc.html
 
Dave Clark
Ranch Hand
Posts: 52
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
you'd be much better off with a JDO-based product than with hibernate - all of the advantages of object-relational mapping technology, but without the single-vendor lockin (API's, query language, configuration and deployment). And most of the major JDO vendors (such as Versant) will be supporting both the JDO 2 and EJB 3 standards.

There are lots of vendors with great JDO products, some of them open source, some commercial. A great resource to go to to compare the vendors is www.jdocentral.com

cheers,

Dave
 
Steven Bell
Ranch Hand
Posts: 1071
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I use hibernate quite often and really like it. As for the 'single vendor lockin' seems to me you could make the same case against Java.

I haven't used JDO much, but I have yet to see anything to interest me enough to put time into it.
 
Dave Clark
Ranch Hand
Posts: 52
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
no - you *can't* make the same case against Java. Java is a specification, with many vendors implementing it. You can get a JVM implementation from Sun, IBM, BEA, others?

Hibernate is a *product*, not a specification (or an open standard). If you build your app with hibernate, then you're stuck with the one and only implementation of hibernate. If you build on JDO, then you can switch JDO vendors without rewriting your app.

cheers,

Dave
 
Steven Bell
Ranch Hand
Posts: 1071
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I was joking a bit, but I still don't see that as a big deal.
 
jacko maxo
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
whatz the big distinction between a "product" and a "spec"? simply the number of people wanting it in the community

there's enough hibernate people out here that it'll be around as long as we "all" want to use it
 
Mark Spritzler
ranger
Sheriff
Posts: 17278
6
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes, there is a distinction. I think when EJB 3.0 comes out we might see a better vision of the future and your choices.

I won't comment further because my views or opinions would spark a lash back by some of our members. Remember Struts and why we got JSF.

Mark
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic