Jakarta Data - Standardized Data Access for SQL and NoSQL Databases
summary
Jakarta Data gives a vendor-neutral API that lets applications swap or mix SQL and NoSQL by defining entities and repository interfaces only, no implementation needed, and promises a five minute getting started. The session compares Spring Data, Micronaut Data, Quarkus/Panache and Jakarta NoSQL, demonstrates Open Liberty + Postgres demo with save/find/delete, shows method name query patterns, annotation queries, pagination pitfalls and keyset pagination, and reports the prototype works for CRUD, sorting and paging across backends.
AI-written summary · about
chapters (11)
- 0:00Introduction to Jakarta Data
- 1:53Trends in 2023 and database challenges
- 9:05Comparison of persistence frameworks
- 17:57Why standardize data access APIs
- 19:02Overview of Jakarta Data
- 20:10Core concepts and repository patterns
- 25:08Query methods and annotations
- 31:26Pagination and sorting techniques
- 35:27Recap of Jakarta Data elements
- 36:10Live demo with Open Liberty
- 43:00Resources and closing
related talks
49mUnlocking Data Access Excellence with Jakarta Data
43mMake your life easier with Jakarta's new persistence features: Data and NoSQL
53mSimplifying NoSQL Database Integration with Jakarta NoSQL
26mUnlocking Data Access Excellence with Jakarta Data
45mSimplifying NoSQL Database Integration with Jakarta NoSQ
47mJakarta EE 12 and the future of Java persistence
32mNoSQL Endgame
54mNoSQL Endgame