Journal dthable's Journal: [programming] Is Hibernate Worth It? 7
I've got into a little debate/argument with a former boss over how to code up a new Java web application. I suggested looking into Hibernate (which I know very little about) to ease up on the developers. He thought we should take control of writing the SQL because there might be too much overhead. Does Hibernate, or any relational mapping library, cause enough slow downs to resort to writing SQL? Is Hibernate really going to make my database and application that much easier to maintain?
I'll be happy to help... (Score:2)
Hibernate won't help your database much, but it will virtually eliminate the need for DAOs. And the overhead is negligible unless you have some REALLY funky table relationships.
Don't forget the lea
Re: (Score:2)
Re: (Score:1)
I'll send you an email so we can talk.
Re: (Score:2)
Hibernate is a lot of work so you can do this:
object.save();
I didn't write the dao. Hibernate already knows if its a save vs an update and automatically pushes the data to the database. No DAOs required, and you can turn on 'see sql' setting in hibernate to know exactly what sql is being run.
Spring gives you 2 things:
1.) A transactional layer with full rollback capability
2.) Aspects so you can make advisors (basi
Hibernate is great (Score:2)
There is a learning curve, but it is by no means insurmoun
ibatis (Score:2)
in fact, the project i am wrapping up uses ibatis as its data abstraction layer (in front of a mysql database but ibatis is just at home with sql server, oracle, db2, sybase etc.)
yeah, there is some weird quirks with ibatis, but its all very workable and its just a nice simple but very powerful and ver
Re: (Score:1)