NoSQL Endgame
summary
Compares Java/JVM persistence layers — Spring Data + MongoDB, Neo4j relationships, Hazelcast demos — against Jakarta NoSQL, Micronaut Data, GORM and Hibernate OGM, with live demos that create, query and delete records via repositories/templates and Postman (adds and removes succeed; Neo4j shows expected graph links). Shows repository vs template patterns, Jakarta NoSQL reduces boilerplate but remains WIP, Micronaut Data currently does not support NoSQL, GORM supports ~3–4 NoSQLs, Spring Data supports roughly half a dozen out of the box, Hibernate OGM is stale; code on GitHub.
AI-written summary · about
chapters (17)
- 0:00Start
- 1:45ABN Amro Bank
- 3:46Advantages of NoSQL
- 6:51Document stores
- 7:16Graph databases
- 7:39Multi-Model
- 7:55SQL vs NoSQL
- 8:41BASE vs ACID
- 9:01CAP
- 9:21Scalability vs Complexity
- 9:44Relational Application
- 11:29Annotated Entities
- 28:33Our example
- 35:18Relationships
- 46:38Operations
- 47:25Conclusions
- 53:23Credits
related talks
32mNoSQL Endgame
47mNoSQL Endgame.
39mFramewars: the battle between NoSQL and Java in the cloud arena
53mSimplifying NoSQL Database Integration with Jakarta NoSQL
43mMake your life easier with Jakarta's new persistence features: Data and NoSQL
51mEmpowering Enterprise Architectures with Polyglot Persistence
45mSimplifying NoSQL Database Integration with Jakarta NoSQ
45mJakarta Data - Standardized Data Access for SQL and NoSQL Databases
