Polyglot Persistence Unleashed
summary
Practical guide to using MongoDB, Cassandra, Neo4j, Redis and Couchbase from Jakarta EE code using Eclipse JNoSQL adapter and Jakarta NoSQL/Jakarta Data APIs, CDI and MicroProfile configurations. Explains Cassandra’s masterless reads and timestamped read‑repair, Redis hashing/replica slots, Neo4j leader/replica model, and document vs column vs key‑value tradeoffs. Shows a Pokemon Entity demo compiled against a single Document/Repository API and run against ArangoDB, MongoDB and Couchbase, proving the adapter approach works.
AI-written summary · about
chapters (15)
- 0:00Welcome to talk
- 0:42Why polyglot persistence matters
- 1:48Database refactoring challenges
- 3:57Polyglot persistence explained
- 4:40Key-value databases overview
- 6:32Redis scalability
- 8:08Column family databases
- 9:44Cassandra architecture
- 12:06Document databases deep dive
- 13:53Graph databases relationships
- 15:40NoSQL trade-offs
- 17:55Standardizing NoSQL with Jakarta NoSQL
- 19:44Eclipse JNoSQL framework
- 22:36Integrating Jakarta specs
- 23:39Closing and resources
related talks
43mMake your life easier with Jakarta's new persistence features: Data and NoSQL
51mEmpowering Enterprise Architectures with Polyglot Persistence
53mSimplifying NoSQL Database Integration with Jakarta NoSQL
46mMastering Java Persistence: Best Practices for Cloud-Native & Modernization
47mMastering Java Persistence: Best Practices for Cloud-Native...
34mSimplifying Polyglot Persistence Integration with...
01h 30mCassandra, Couchbase and Spring Data in the Enterprise
46mGetting Started with Jakarta NoSQL and MongoDB
