On-demand nested entities in APIs with Spring Data JPA
summary
Shows how to build a request handler that lets API clients request nested related entities on demand using Spring Data JPA. Compares Spring Data REST and Spring GraphQL features and limits, then presents a custom Spring Data JPA extension implementation, plus discussed problems encountered and ways to solve them.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:19Nested entities problem
- 8:32Spring Data REST limits
- 11:21Solution with Spring Data JPA
- 13:51Dynamic graph demo
- 15:36Data conversion issues
- 20:55Performance problems
- 25:15Query optimization
- 27:44Data caching
- 31:02GraphQL comparison
- 33:38Current approach drawbacks
- 37:12Solution benefits
- 39:28Conclusion & Q&A
related talks
01h 31mSpring Data REST: Easily export JPA entities directly to the web
49mExtending Spring Data
01h 05mJPA Puzzlers (+Hibernate and Spring)
49mPerformance oriented Spring Data JPA & Hibernate
50mSpring Data JPA - The Swiss Army Knife for Data Access
50mSpring's unexpected features
01h 32mSpring Data Repositories -- A Deep Dive
59mFrom CRUD to Hypermedia API with Spring