Hi,

We are evaluating whether we should develop out persistent objects using a framework like hibernate or use JDBC and Data Object and code the same ourselves.

Though the argument is quite mute, does any one have any specific metrics in terms of overall time reduction with Hibernate as against the standard JDBC-SQL.

Thanks,

Anand

there might be 1 000 000 posts talking about that here...
i'll advice you not to deal with such tests until you are an expert of concurrency, transaction ....

ORM is NOT a data acces tool! so don't compare it to JDBC, it offers you much more...

Appreciate your response. I do agree that ORM offers much more than raw data access but for commerical projects, when we need to justify the choice of a framework, two things are asked: 1. Training Needs,2. How much is the developmment time going to come down by using the framework.

If you could point me to some place where I can get the information I asked, i woudlg reatly appreciate that.

ORM tools don't take away anything from SQL/JDBC, as they allow you full transparent access to the language and API whenever you need. Therefore, your development time _with_ an ORM tool never will be slower than without. Consider the additional features you get using ORM software, and check for each feature if its a) worth using in your scenario and b) how likely will it introduce new problems and c) how hard is it to learn. If the net result looks positive, use it.

My experience tells me that many features an ORM tool can provide have a positive impact on development performanc and personal happyness of the developer (and hopefully the DBA). See my blog entry a few days ago about "Comparing ORM tools", might be related.

http://blog.hibernate.org/cgi-bin/blosx ... ersistence

excuse me for my answer, i understood you were talking about performance... sorry
you should talk about transaction and concurrency management that secure you application for example.
You should talk about performance.
You can also say that developpeur will work most of the time on the business and not on the technical aspects.
Hibernate allows you to work in a full OO mind, which allows you to reuse the code.
Developpers must only think object, even for querying, they don't have to be expert in sql for example.

oh and last thing:


you are 100% right, don't hesitate training your guys because even if hibernate simplify your life, it is always possible to make big mistakes if you don't understand how to use it.

Chritian

That's a great blog. More than anything, I was looking for a justification to my decision to go with Hibernate (you guys rock..). since I was asked to get some quantifiable metrics on hibernate since it was a new framework, open source(quite ironic don't you think), etc.

As Anthony righly put it developers should be talking objects and not tables and columns.

Thanks for all your inputs.
-Anand

I just end a project where 1 spend 1 single day solving lecacy mistakes (especially performance issues). Have 1 Hibernate expert in your team is the best solution I know.

I agree with the training as well. This is key to a successful ORM Project.
At least you should have developers in the team who are willing to read a lot before they start coding with a new ORM Tool instead of "hacking straight away and see what happens"