High-performance Java Persistence.pdf May 2026

Vlad Mihalcea’s work stands out because it is not academic. It is pragmatic. For every pattern (e.g., "Use a DTO projection"), there is a counter-pattern (e.g., "Avoid DTO projections for graph of objects") with specific benchmarks to prove the point.

Whether you use PostgreSQL, MySQL, or Oracle, the principles of batching, fetching, and caching inside this document are timeless. Find the official source, pay for the knowledge, and watch your application latency drop by an order of magnitude. High-performance Java Persistence.pdf

List<Post> posts = entityManager.createQuery("from Post", Post.class).getResultList(); for(Post p : posts) { p.setStatus(Status.OLD); } // Hibernate will send UPDATE 1, UPDATE 2, UPDATE 3... Vlad Mihalcea’s work stands out because it is not academic

int updatedEntities = entityManager.createQuery( "update Post set status = :newStatus where createdOn < :date") .setParameter("newStatus", Status.OLD) .setParameter("date", LocalDate.now().minusDays(30)) .executeUpdate(); // Sends 1 SQL statement. The PDF spends pages explaining why the first loop kills your performance (transaction bloat, row lock escalation, and network round trips) and how to identify this using the logger, a tool the author created. Is the PDF Relevant in the Age of Spring Boot 3 & Native Compilation? Absolutely. With the rise of GraalVM Native Image , persistence has become tricky again. Reflection, proxies, and dynamic bytecode generation (Hibernate's specialty) often break native compilation. Whether you use PostgreSQL, MySQL, or Oracle, the