Do you really need Hibernate?
summary
Demo builds a kids competition app and shows concrete replacements for Hibernate: it uses jOOQ + Java Records to generate a type-safe meta model from Flyway migrations, runs in testcontainers, and executes a single query that returns nested DTOs via multiset to return nested JSON. The project scales to large schemas — an example with ~2,000 tables generates ~10,000 classes and compiles — and the approach avoids N+1 selects and works alongside JPA when needed.
AI-written summary · about
chapters (16)
- 0:00Introduction and background
- 3:36Business applications and database centricity
- 5:04JPA vs SQL: Entity state vs data set transformation
- 10:06Introduction to JOOQ and its approach
- 14:17JOOQ in action: Code generation and usage
- 22:03Reading and updating data with JOOQ records
- 26:44Type safety and database agnosticism with JOOQ
- 30:24Reading nested structures with JOOQ
- 36:04Generating database model with JOOQ
- 42:06Do you really need Hibernate?
- 45:37Q&A session part 1
- 47:59Q&A session part 2
- 50:28Q&A session part 3
- 51:17Query details for nested structures
- 52:24Non-relational databases and JOOQ
- 53:52Final Q&A and closing
related talks
54mDo you really need Hibernate
49mDo You Really Need Hibernate?
43mDo You Really Need Hibernate?
46mThe State of Java Relational Persistence
50mCreate Your Perfect Persistence Stack
51mThe Persistence Heavyweight Championship: JPA vs. jOOQ
47mThere is always a choice. Spring Data JDBC vs. Hibernate. Taras Boychuk. Java Fest 2020 Online
34mSimplifying Polyglot Persistence Integration with...