• 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

Persistence in the Enterprise - Hibernate the top?

 
Ranch Hand
Posts: 99
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hibernate is still the top framework or there is something better? Are there emergent framework that looks very good?

thanks!
 
Ranch Hand
Posts: 471
Mac OS X Hibernate Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
IMHO, there is no better. There is better for your specific case. Trying to find the best framework would only lead to a very long thread with a debate that will not lead to something useful. I for myself love hibernate, but of course some other frameworks have advantages over it.
 
author
Posts: 22
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
See Chapter 4 of the Persistence in the Enterprise Book for a questionnaire to use to make the determination in your own culture and environment. Chapter 10 summarizes the evaluations we make for JDBC, iBatis, Hibernate Core, Open JPA and PureQuery in one place for easy reference.

I have also been driving IBM towards an approach called Pattern based Engineering, which is all about developing your own best practices and capturing various templates to automate the tedious, error prone parts.
The reason I bring it up is that every framework is going to have some disadvantages in your specific circumstances. By using a templating engine, you can pretty easily "paper over" them until they improve. It also makes it easier to switch frameworks underneath the covers.

I hint at this in Chapter 10. For more details, check out chapter 16 of a recent IBM Redbook:

Strategic Reuse with Asset based Development (IBM Redbook):
http://www.redbooks.ibm.com/redpieces/abstracts/sg247529.html?Open

Ok then, Geoff
reply
    Bookmark Topic Watch Topic
  • New Topic