Cause of Death: Hibernate.
summary
Shows concrete Hibernate pitfalls with code and numbers: eager fetch turns one query into N+1 (6 authors → 7 JDBC statements), list vs set causes wholesale delete+inserts on many-to-many, JPQL bulk updates require flush+clear or first-level cache hides changes, missing association cache forces 24–36 extra statements until entity+collection caches are enabled, and bi‑directional cascade remove can delete most of your data with just one annotation. Covers open session in view anti-pattern and a new library to bring the database to its knees with thousands of queries and how to fix each.
AI-written summary · about
chapters (12)
- 0:00Introduction and welcome
- 3:22Hibernate performance pitfalls
- 10:54Many-to-many mapping issues
- 18:59Hibernate caching explained
- 27:06Query cache best practices
- 31:22Inconsistent results with Hibernate
- 36:22JPQL update statements risks
- 39:13Bidirectional associations handling
- 41:44Open session in view anti-pattern
- 49:31Batch processing and entity clearing
- 50:58Cascading remove dangers
- 53:44Q&A and closing remarks
related talks
16mCause of Death: Hibernate
52mCause of Death: Spring Data JPA
45mLazy Versus Eager Loading Strategies for JPA 2.1
44mORM Insights - How not to hurt yourself?
48mORM Iinsights - How to Not Hurt Yourself?
42mJPA - Beyond copy-paste
47mWhen ORM Becomes OMG: Performance Pitfalls in JPA and Friends
52mJava Persistence and Hibernate Tips that can boost up your application performance