iBATIS Hibernate - iBATIS

What are the differences between Ibatis and Hibernate ?

This chapter explains about the major differences between iBATIS and Hibernate. iBATIS is suggested in case −
  • To create your own SQL's and you are willing to maintain them.
  • If your To Environment is driven by relational data model.
  • To work on existing and complex schemas.
Incase if you use Hibernate when the environment is driven by object model then it needs to generate SQL automatically.

What are the differences between iBATIS and Hibernate?

Both Hibernate and iBATIS are open source Object Relational Mapping (ORM) tools available in the industry. The usage of each tool depends on the context you are using them.
The following table highlights the differences between iBATIS and Hibernate −



iBATIS is simpler. It comes in a much smaller package size.

Hibernate generates SQL for you which means you don’t have to spend time on generating SQL.

iBATIS is flexible. It offers faster development time.

Hibernate is highly scalable. It provides a much more advanced cache.

iBATIS uses SQL which could be database dependent.

Hibernate uses HQL which is relatively independent of databases. It is easier to change db in Hibernate.

iBatis maps the ResultSet from JDBC API to your POJO Objets, so you don’t have to care about table structures.

Hibernate maps your Java POJO objects to the Database tables.

It is quite easy to use stored procedure in iBATIS.

Use of stored procedures is a little difficult in Hibernate.

It is difficult to choose one among Hibernate and iBATIS as both of them receive good support from the SPRING framework.

All rights reserved © 2020 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

iBATIS Topics