• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

should I use Hibernate on fairly small project?

 
Ranch Hand
Posts: 161
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I will soon build a small web project. The project will enable query, search, and display digital images and their metadata. The metadata will be stored in a relational database. The system will also perform unicode searching on the metadata using Lucene. Later, we will provide for updates (full Crud). For now, queries will be suffient. I am experienced with SQL and JDBC.

What do you all think? Should I use Hibernate? Is it stable? Do you find yourself debugging database persistence framework code? Or do you think it is worth using, even for simpler projects? Or would a few data access objects with some raw SQL turn the trick a lot faster?
 
Ranch Hand
Posts: 547
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi Benjamin

Hibernate is well tested, stable and has an active community. You wont find bugs if you just use the basic features...

One thing that could be useful for you is the hibernatelucene integration: http://www.hibernate.org/hib_docs/annotations/reference/en/html/lucene.html


If it's worth for your project to learn hibernate i can not tell. Perhaps a simpler (more JDBC oriented) framework like iBatis is easier to learn. I do not think your project would be hurt by using hibernate... so if you get the time to learn (it's not that complicated to get it up and running with basic operations but it takes some rading andd experimenting) i would do so...


pascal
 
Ranch Hand
Posts: 190
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Remember that 80% of a programs life is maintainance. The program is bound to change, and that usually means growing. So even though the program is going to start small you have no idea where it may end up. I would say Hibernate is would be a good choice.
 
Benjamin Weaver
Ranch Hand
Posts: 161
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for your replies. I think for now I will go with iBatis, then learn Hibernate as I go along and perhaps eventually switch to it. I have not been coding for a while and do not have the confidence that more senior developers have in using a persistence layer that hides more of itself under the hood. As we move on, our app gets bigger, and as I get more comfortable with Hibernate and do not have to show immediate results, I will likely make the switch. A true persistence layer that enables saving of object graphs is a good thing if one is comfortable with it.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic