Make your life easier with Jakarta's new persistence features: Data and NoSQL
summary
Jakarta introduces two concrete persistence specs: Jakarta NoSQL for document/key‑value/graph/column stores and Jakarta Data for a repository API over SQL or NoSQL. A demo runs MongoDB, Couchbase and ArangoDB via Docker Compose, uses Java records for Pokemon entities, and shows a common Template API plus specializations (document/column/graph) and a pageable repository. Aggregation support is not yet implemented, AQL ID handling shows a known bug, and the Jakarta/Eclipse JNoSQL implementations work end to end for inserts, queries and pagination.
AI-written summary · about
chapters (10)
- 0:00Introduction and Jakarta overview
- 2:03Why Jakarta NoSQL matters
- 11:22Live demo setup and entity creation
- 19:15Template and injection explained
- 21:46Querying and filtering with templates
- 29:22Switching databases with specialization
- 33:22Introducing Jakarta Data repository
- 37:01Repository save and find operations
- 39:08Pagination with repositories
- 41:42Q&A and closing remarks
related talks
45mJakarta Data - Standardized Data Access for SQL and NoSQL Databases
25mPolyglot Persistence Unleashed
45mSimplifying NoSQL Database Integration with Jakarta NoSQ
47mJakarta EE 12 and the future of Java persistence
50mJakarta Data and Jakarta Persistence
26mUnlocking Data Access Excellence with Jakarta Data
46mGetting Started with Jakarta NoSQL and MongoDB
50mJakarta Data and Jakarta Persistence