Hibernate VS JDO- - - which one?

[Yan Lee]

Hi,
I am looking to use either Hibernate or JDO in my J2EE application.
Since I am new to both, I am unable to decide on either one.

Please advise:
[1] Is one bettter than the other? Why?
[2] If JDO is better which implementation is advisable?
[3] How do they perform in production environment in terms of speed?

Thanks.

[Pj Murray]

Originally posted by Yan Lee:

Please advise:
[1] Is one bettter than the other? Why?

That all depends on the skills available and the specific application you're developing.

This comparison of the Java persistence technologies might help:

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

Originally posted by Yan Lee:

[2] If JDO is better which implementation is advisable?

There's several good commercial implementations. But I'd advise looking at Apache JDO.

http://db.apache.org/jdo/

Originally posted by Yan Lee:


[3] How do they perform in production environment in terms of speed?

If you have a need for speed, you may not necessarily want to use an ORM approach. For raw application speed, you might just want to use a straight JDBC (perhaps with the DAO design pattern to give it some structure).


.

[Erik Bengtson]

Originally posted by Yan Lee:
Hi,
I am looking to use either Hibernate or JDO in my J2EE application.
Since I am new to both, I am unable to decide on either one.

Please advise:
[1] Is one bettter than the other? Why?
[2] If JDO is better which implementation is advisable?
[3] How do they perform in production environment in terms of speed?

Thanks.

[1] Why don't you try by yourself? If one definitive answer for persistence existed, no one would survive besides it.

[2] you can try http://www.jpox.org

[3] http://www.jpox.org/docs/performance.html

I will suggest you to try both, and see what you like better. Don't stand with the "Yes, our product rocks!" or "We know best".

[Pj Murray]

Originally posted by Erik Bengtson:


[1] Why don't you try by yourself? If one definitive answer for persistence existed, no one would survive besides it.

This is very true. There's is NO perfect persistence technology and all of them have advantages and disadvantages. You need to keep your options open - even open to the possibility of changing persistence technology during the lifetime of an application (e.g. move from JDO to EJB 3 next year).

You should design your application to ensure that the underlying persistence technology can be changed without affecting the rest of your application (the reason why I recommend using DAOs on top of the technology layer).

Originally posted by Erik Bengtson:


[2] you can try http://www.jpox.org

That's right, I should have listed JPOX as the best open source JDO available at the moment. I just listed Apache because it has good industry support and a brand name so it might be easier to get accepted in a commercial project.