Spring Data JDBC - Taming the Beast
summary
Spring Data JDBC targets Spring microservices and deliberately trades JPA features for simplicity: it inserts the root then children, issues a separate select per child on reads, and on update deletes all child rows and reinserts them (so a 150-review example forces full resnapshot), which lengthens transactions and acquires locks in PostgreSQL. Use composite keys and single-query loading when needed, but follow one rule: start small: one aggregate per entity unless you have a strong reason to merge, and prefer entities for children if independent updates matter.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 4:23Spring Data JDBC overview
- 10:04Monoliths to microservices
- 23:07Why Spring Data JDBC fits
- 29:00Designing aggregates
- 33:15Entities vs value objects
- 39:13Best practices
- 41:00Q&A
related talks
47mThere is always a choice. Spring Data JDBC vs. Hibernate. Taras Boychuk. Java Fest 2020 Online
49mPerformance oriented Spring Data JPA & Hibernate
46mThe State of Java Relational Persistence
52mSpring Data JDBC. Known problems, unknown problems
31mJDBC, What Is It Good For?
34mThe Complexity of JPA
49mDo You Really Need Hibernate?
44mPerformance oriented Spring Data JPA & Hibernate