ORM Insights - How not to hurt yourself?
summary
More than half of application performance bottlenecks trace to the database, so the talk demonstrates concrete JPA/Hibernate pitfalls and fixes: how persistence context snapshots and dirty checking use memory and CPU during flush, how lazy associations create N+1 queries and when to use join fetch, entity graphs or batch fetching, and how optimistic locking via @Version and optimistic-force-increment prevents lost updates. Alternatives and patterns include Spring Data JDBC, jOOQ, native queries, and the outbox pattern for reliably dispatching events after transaction commit.
AI-written summary · about
chapters (6)
- 0:00Introduction and speaker intro
- 3:00Entity states and dirty checking
- 15:32Associations and loading strategies
- 24:49N+1 problem and solutions
- 32:48Transactions and locking
- 39:05Alternatives and resources
related talks
48mORM Iinsights - How to Not Hurt Yourself?
47mWhen ORM Becomes OMG: Performance Pitfalls in JPA and Friends
58mCause of Death: Hibernate.
45mWhen ORM Becomes OMG: Performance Pitfalls in JPA and Friends
44mPerformance oriented Spring Data JPA & Hibernate
52mJava Persistence and Hibernate Tips that can boost up your application performance
51mWhen ORM Becomes OMG: Performance Pitfalls in JPA and Friends
49mPerformance oriented Spring Data JPA & Hibernate