Framewars: the battle between NoSQL and Java in the cloud arena
summary
Compares MongoDB Redis Neo4j Cassandra and “over 200 implementations” of NoSQL and maps real trade‑offs to Java options: raw drivers (example: five lines to insert a MongoDB document), object mappers (reduce boilerplate but cause impedance), specific APIs (use Cassandra CQL or Neo4j features) and agnostic APIs (lag on specialty features). Surveys platforms: Spring Data most mature, Quarkus active‑record and repository options, Micronaut compile‑time injection, Hibernate OGM’s awkward transactions, and Jakarta NoSQL + TinkerPop emerging as a standard.
AI-written summary · about
chapters (17)
- 0:00Introduction to Framewars
- 1:03NoSQL databases overview
- 3:49NoSQL database types explained
- 8:31Graph databases and relationships
- 11:00Challenges with NoSQL in Java
- 13:25Java framework communication levels
- 17:02Object mappers in Java
- 19:27Specific APIs for NoSQL
- 21:57Agnostic APIs for NoSQL
- 22:40Platforms for Java and NoSQL
- 24:05Hibernate OGM deep dive
- 27:20Quarkus for NoSQL
- 29:49Micronaut with NoSQL
- 31:15Spring Data for NoSQL
- 33:03Standards in NoSQL APIs
- 35:53Jakarta NoSQL framework
- 38:25Summary and closing remarks
related talks
32mNoSQL Endgame
47mNoSQL Endgame.
54mNoSQL Endgame
45mSimplifying NoSQL Database Integration with Jakarta NoSQ
45mNoSQL: Death to Relational Databases
51mEmpowering Enterprise Architectures with Polyglot Persistence
50mNoSQL Databases You Have to Know
53mSimplifying NoSQL Database Integration with Jakarta NoSQL
