Simplifying NoSQL Database Integration with Jakarta NoSQ
summary
Jakarta NoSQL + Jakarta Data claim to let Java apps talk to many NoSQL engines with a JPA-like API; the live demo uses Quarkus, MicroProfile, WebSocket events and a simple game app that persists via a JNoo reference implementation to MongoDB then to Couchbase. JNoo already supports about 30 databases (uploader mentions 118 vendors in the ecosystem), uses annotations and records supported, maps entities to key‑value, document, wide‑column and limited graph models, and swapping vendor is just a config change.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 1:22What is NoSQL and its families
- 6:44Challenges with NoSQL vendors
- 10:00Jakarta NoSQL specification
- 13:37How Jakarta NoSQL works behind the scenes
- 18:18Demo introduction and setup
- 23:42Live game demo with MongoDB
- 28:47Switching databases easily
- 32:22Configuration and dependencies
- 34:30Workshop and community resources
- 36:44Q&A session
related talks
53mSimplifying NoSQL Database Integration with Jakarta NoSQL
43mMake your life easier with Jakarta's new persistence features: Data and NoSQL
45mJakarta Data - Standardized Data Access for SQL and NoSQL Databases
39mFramewars: the battle between NoSQL and Java in the cloud arena
54mNoSQL Endgame
34mSimplifying Polyglot Persistence Integration with...
47mJakarta EE 12 and the future of Java persistence
46mGetting Started with Jakarta NoSQL and MongoDB