The State of Java Relational Persistence
summary
Covers concrete tradeoffs and working examples: Hibernate/JPA hides many pitfalls (cascades, unexpected schema, N+1 queries) and benefits from a commercial Hibernate Persistence Optimizer; jOOQ generates type‑safe SQL from the database and prevents string‑concatenation bugs for complex reads; Spring Data JDBC is opinionated, enforces aggregates by ID and requires explicit save (no lazy/dirty tracking); R2DBC provides a nonblocking SQL client for reactive apps; Testcontainers spins up real Postgres/Aurora instances for reliable integration tests.
AI-written summary · about
chapters (5)
- 0:00Start
- 6:52RELATIONAL DATABASES ARE MORE FORGIVING
- 24:41HIBERNATE & JPA IS NOT THE ALTERNATIVE TO SQL. SQL IS YOUR FRIEND.
- 31:15SPRING DATA JDBC
- 39:25BASED ON JDBC BLOCKING
related talks
49mDo You Really Need Hibernate?
43mDo You Really Need Hibernate?
51mThe Persistence Heavyweight Championship: JPA vs. jOOQ
54mDo you really need Hibernate
47mThere is always a choice. Spring Data JDBC vs. Hibernate. Taras Boychuk. Java Fest 2020 Online
34mThe Complexity of JPA
01h 49mJPA Essentials Workshop – Fundamental Concepts and Common Pitfalls
51mEmpowering Enterprise Architectures with Polyglot Persistence