• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Persistance in the enterprise book

 
Mohamed Mabrouk
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello
In a small sized solution with a limited set of objects saved, is it worth to induce hibernate or will it be an overhead and one should stick to entity beans?

Does the book compare between alternate persistence solutions and when to use what?
 
Adeel Ansari
Ranch Hand
Posts: 2874
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Mohamed Mabrouk:
In a small sized solution with a limited set of objects saved, is it worth to induce hibernate or will it be an overhead and one should stick to entity beans?


I believe, there might be no need of Entity Beans, too. In fact, it depends on the requirements and complexity involved and things like that.

Its very simple, consider things which are provided by Hibernate or any other ORM Tool, and then ask a question to yourself, whether its needed or not. Quire simple isn't it.

Cheers.
 
Roland Barcia
author
Ranch Hand
Posts: 181
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This book is all about comparing persistence frameworks, and we do discuss Hibernate.

Since Entity Beans have fallen out of favor, we discuss Open JPA.

Your question on not too many objects is probably not a Hibernate versus CMP question, but rather SQL Based Framework (iBatis, pureQuery) vs an ORM one (Hibernate, JPA, etc...).

Does your application spend more time/use cases accessing/manipulating data through accessor methods or do you access data more through some query (SQL or Object query)? If your application spends more time accessing data through some query language, maybe a full ORM is not a right solution and you should look at iBatis or pureQuery.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic