Do you really need Hibernate
summary
Argues many CRUD-heavy apps don’t need Hibernate’s ORM overhead and shows a working alternative: a 25‑year application migrated to jOOQ + Java Records, DB‑first generation from migrations, and Maven plugin codegen. Demonstrates one‑statement nested reads via multiset→nested JSON to avoid n+1 selects, stored‑procedure wrappers, and type‑safe compile‑time SQL; uses testcontainers+Flyway for generation and tests. Shows code in simasch/jooq-examples and claims better performance with less runtime magic.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 7:49JPA vs CRUD approach
- 11:20jOOQ core concepts
- 15:35jOOQ in Maven
- 22:39CRUD with jOOQ
- 27:11Projections and type safety
- 32:56Complex nested data structures
- 37:57jOOQ with Testcontainers
- 39:06jOOQ superpowers
- 41:17Avoid raw SQL strings
- 42:00Q&A
related talks
49mDo You Really Need Hibernate?
43mDo You Really Need Hibernate?
54mDo you really need Hibernate?
46mThe State of Java Relational Persistence
51mThe Persistence Heavyweight Championship: JPA vs. jOOQ
50mJOOQ Data Abstractions Without Distraction
46mjOOQ as an Alternative to ORM
48mCQRS in the small with Java Records and jOOQ