i) Hibernate is better then plain JDBC, you can use Hibernate which generates
the SQL on the fly and then automatically executes the necessary SQL statements.
This saves a lot of development and debugging time of the developer. Writing
JDBC statement, setting the parameters, executing query and processing the result
by hand is lot of work. Hibernate will save all tedious efforts.

ii) When you compare with EJB, Hibernate persistence has no requirement for
a J2EE application server or any other special environment. It is, therefore,
a much more suitable solution for stand-alone applications, client-side application
storage, and other environments in which a J2EE server is not immediately available.

iii) Hibernate uses POJOs so these POJOs can be used for different purposes
also like DTOs etc.,

iv) Hibernate does not require you to map one POJO to one table. A POJO can be
constructed out of a selection of table columns, or several POJOs can be persisted
into a single table.
 
v) Hibernate directly supports inheritance relationships and the various other relationships
between classes.

vi) Any Java object capable of being persisted to a database is a candidate for
Hibernate persistence. Therefore, Hibernate is a natural replacement for ad hoc
solutions, or as the persistence engine for an application that has not
yet had database persistence incorporated into it. Furthermore, by choosing Hibernate
persistence,you are not tying yourself to any particular design decisions for
the business objects in your application.
 
vii) JPA Provider: Hibernate can work as JPA provider in JPA based applications.

Back to top