Simplifying NoSQL Database Integration with Jakarta NoSQL
summary
Jakarta NoSQL with Jakarta Data offers a JPA‑like API for multiple NoSQL stores and the demo builds a Rock‑Paper‑Scissors game that persists plays; swapping backends requires only adding the provider dependency and changing MicroProfile config so MongoDB becomes Couchbase, repositories use Spring‑Data style methods, CDI handles events, and records map as entities. The implementation claims support for 30+ vendors and for key‑value, wide‑column and document families (Jakarta LE adds graph via Apache TinkerPop); the live demo stores events and runs after a brief restart hiccup.
AI-written summary · about
chapters (9)
- 0:00Introduction and motivation
- 2:36NoSQL overview and families
- 10:47Challenges with NoSQL vendors
- 13:58Jakarta Data and Jakarta NoSQL
- 20:45Jakarta Data repository concept
- 29:23Game demo introduction
- 35:49Setting up Jakarta NoSQL in code
- 42:46Switching databases with configuration
- 48:15Resources and conclusion
related talks
45mSimplifying NoSQL Database Integration with Jakarta NoSQ
45mJakarta Data - Standardized Data Access for SQL and NoSQL Databases
54mNoSQL Endgame
34mSimplifying Polyglot Persistence Integration with...
25mPolyglot Persistence Unleashed
49mUnlocking Data Access Excellence with Jakarta Data
32mNoSQL Endgame
46mGetting Started with Jakarta NoSQL and MongoDB