Unlocking Data Access Excellence with Jakarta Data
summary
Jakarta Data delivers a cross-database repository pattern that works with JPA/Hibernate and NoSQL via providers like Eclipse JNoSQL provider, supporting method-name queries and @query annotations so code stays domain-centric. Demo runs a snapshot project that generates 100 fake beers with DataFaker, saves them through a repository, and exercises findBy-style, sorting, offset pagination and more efficient cursor pagination (use a unique ID). The first release focuses on repository semantics and query-by-method conventions.
AI-written summary · about
chapters (19)
- 0:00Introduction and welcome
- 0:51Why database matters today
- 2:58Polyglot persistence explained
- 4:44Developer vs DBA challenges
- 7:33Persistence patterns overview
- 9:22Introducing Jakarta Data
- 11:07Entities and repositories
- 17:40Live coding demo setup
- 19:37Creating repository interface
- 21:47Generating and saving data
- 23:12Cross-database repository benefits
- 23:56Query methods by convention
- 25:03Query annotations and actions
- 28:18Sorting query results
- 30:31Jakarta Data Query Language
- 33:51Pagination with offset
- 37:06Cursor-based pagination
- 42:27Jakarta Data ecosystem overview
- 43:31Q&A session
related talks
26mUnlocking Data Access Excellence with Jakarta Data
45mJakarta Data - Standardized Data Access for SQL and NoSQL Databases
48mManaging Data in Jakarta EE Applications
43mMake your life easier with Jakarta's new persistence features: Data and NoSQL
53mSimplifying NoSQL Database Integration with Jakarta NoSQL
50mJakarta Data and Jakarta Persistence
50mJakarta Data and Jakarta Persistence
46mGetting Started with Jakarta NoSQL and MongoDB