What approaches did you use to eliminate the N+1 query problem in Hibernate and how did you implement it?

The N+1 query problem in Hibernate occurs when a collection of entities is loaded, and for each entity, a separate query is executed to load related data, leading to N+1 total queries, which severely impacts performance.

Main approaches to fix this:

1. Use JOIN FETCH in JPQL/HQL — loads related entities in a single query using join.

String hql = "SELECT p FROM Parent p JOIN FETCH p.children";
List<Parent> parents = session.createQuery(hql, Parent.class).getResultList();

2. Entity Graphs — declarative way to specify which associations to load eagerly.

3. FetchType.EAGER — eager loading, but use carefully to avoid unnecessary data loading.

4. Batch fetching — configure Hibernate to load related entities in batches, reducing query count.

5. Use @Fetch(FetchMode.SUBSELECT) — Hibernate loads collections with a subselect in one additional query.

Choice depends on specific situation and performance requirements.