No PDF cheat sheet teaches you that—because it is an architectural pattern, not a Hibernate property. Every "High-Performance Java Persistence" summary tells you to use JOIN FETCH carefully. They warn about Cartesian products.
Imagine an auction system. Ten users bid on the same item. With @Version , nine users will get OptimisticLockException . You retry. The database churns. Performance collapses. high-performance java persistence book pdf
But the truly interesting performance hack involves . No PDF cheat sheet teaches you that—because it
Most developers do this:
Here is the uncomfortable truth:
// Fast: Fetches only what you need, immutable, no persistence context overhead List<PostDTO> posts = entityManager.createQuery("select new com.dto.PostDTO(p.id, p.title) from Post p", PostDTO.class).getResultList(); Why is this faster than the book's PDF suggests? Because you remove the Entity Manager from the equation. No snapshots. No comparisons. Just data transfer. Vlad Mihalcea’s book is fantastic, but the concepts evolve faster than print. If you search for a static PDF, you freeze your knowledge in time. Imagine an auction system