Hibernate for small application

Hi,

Should we use hibernate for small applications where some files will be uploaded and the records from the file will be saved into the db.

one might need to handle around 500-100 records in a single insert/update/select transaction.

I feel datasources are good enough to handle this much data. will hibernate be an overhead in this much data ?

Thanks,
Neeraj.

Up to you really. The size of the application doesn't particularaly matter - I'd personally use Hibernate for most DAO logic these days, unless the application was very basic, or a bulk loader.

Its not the volume of data that should be driving your decision, its portability and ease of use. If you go with JDBC, you will have to write all the nuts and bolts to convert from entities to objects yourself. No biggy if there are not many entities. But if you ever have to change to a different database Hibernate is a godsend.

Whatever you choose, assuming you use a data access pattern you should be able to swap your persistence technology easilly enough.

I love hibernate as much as the next guy, but sometimes a good ETL tool like DataStage is worth the effort, especially if you have a license hanging around.

It's always about having the right tool for the job.

-Cameron McKenzie

O/R mapping is well suited for read --> modify --> write centric applications and not suited for write centric applications (i.e. batch processes with large data sets like 5000 rows or more) where data is seldom read. Although this was generally true of many earlier O/R mapping frameworks, most today (including Hibernate) allow for efficient ways of performing large batch style write operations.