Say YES! to NoSQL: A Guide on When to Ditch Relational Databases
summary
Practical checklist: if data shows high data volume, high data velocity, large variety or strong valence, favor NoSQL; choose by guarantees next: prefer BASE/fast writes and horizontal scaling for typical NoSQL workloads, or use ACID when multi-document transactions matter — MongoDB (multi-document ACID since 4.2) and Neo4j offer ACID, Cassandra favors availability for wide‑column scale, Redis or RocksDB suit key‑value speed. Use the three‑step sieve: data characteristics → consistency model → CAP filter to pick model and database that actually meets latency, write throughput, and schema‑change needs.
AI-written summary · about
chapters (12)
- 0:00Introduction to NoSQL
- 1:06Relational databases vs NoSQL
- 2:31NoSQL data models explained
- 5:46Is NoSQL better than SQL?
- 6:28CAP theorem fundamentals
- 18:37ACID vs BASE properties
- 21:44Three-step NoSQL guide
- 23:13Evaluating data characteristics
- 34:54Choosing consistency models
- 38:25Final CAP filter and tech choice
- 40:52Rethinking tech selection
- 41:33Q&A and closing
related talks
45mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
45mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
38mNoSQL Databases: Its not a free lunch
01h 00mFrom Relational Databases to NoSQL
19mRelational or Non-Relational? Choosing the Best Database for the Task
19mRelational or Non-Relational? Choosing the Best Database for the Task
01h 01mNoSQL: An Analysis
45mNoSQL: Death to Relational Databases