Understanding Hibernate: Benefits, ORM Basics, Query Types, Session Management, Caching, and Entity Rules

Hibernate is a mainstream Java persistence framework built on JDBC that encapsulates database access code, greatly simplifies the DAO layer, uses reflection for transparency, and offers high performance with flexible mapping across many relational databases.

ORM (Object‑Relational Mapping) is middleware that maps in‑memory objects to relational tables, allowing developers to work with objects while the framework handles the conversion to SQL.

To view the SQL statements generated by Hibernate, you can enable logging as described in the referenced blog post.

Hibernate supports three query approaches:

HQL (Hibernate Query Language) – object‑oriented queries, e.g.,

Query query = session.createQuery("from Customer where name = ?"); query.setParameter(0, "Example"); query.list();

Criteria (QBC – Query By Criteria) – programmatic conditional queries, e.g.,

Criteria criteria = session.createCriteria(Customer.class); criteria.add(Restrictions.eq("name", "Example")); List<Customer> list = criteria.list();

Native SQL – direct SQL execution, e.g.,

SQLQuery query = session.createSQLQuery("select * from customer"); List<Object[]> list = query.list();

Entity classes can be declared final, but doing so prevents Hibernate from creating proxy subclasses needed for lazy loading, which may degrade performance; using interfaces can mitigate this limitation.

When mapping identifiers, using Integer allows Hibernate to detect transient objects via null values, whereas int requires setting unsaved-value="0" in the mapping file.

Typical Hibernate workflow:

Load configuration: Configuration config = new Configuration().configure(); Parse mapping resources from hibernate.cfg.xml.

Create SessionFactory: SessionFactory sf = config.buildSessionFactory(); Open a Session: Session session = sf.openSession(); Begin a transaction: Transaction tx = session.beginTransaction(); Perform persistent operations (save, update, delete, query).

Commit the transaction: tx.commit(); Close the session and finally the SessionFactory.

The get() method immediately hits the database and returns a fully initialized object, while load() returns a proxy and only queries the database when a non‑identifier property is accessed.

Hibernate caches data at two levels: first‑level cache (session scoped, always enabled) and optional second‑level cache (session‑factory scoped). Suitable data for second‑level caching includes rarely modified, frequently read, non‑critical, or constant data; distributed caches like Memcached or Redis can be used as alternatives.

Entity objects exist in three states:

Transient – newly instantiated, not associated with a session, no identifier.

Persistent – associated with a session after save() or saveOrUpdate(), has an identifier.

Detached – the session has been closed, the object is no longer managed.

Session acquisition differs: openSession() always creates a new session that must be closed manually, whereas getCurrentSession() returns the current transactional session, creating one if none exists, and is preferred in modern applications.

Hibernate requires entity classes to have a no‑argument constructor because it uses Class.newInstance() to instantiate objects; if you define other constructors, you must explicitly provide the default constructor.