Say YES! to NoSQL: A Guide on When to Ditch Relational Databases
summary
NoSQL is framed as a decision process: first measure your data’s volume velocity variety valence (large volume, high write rate, diverse formats, or dense connections push toward NoSQL), then choose consistency guarantees with ACID vs BASE (note MongoDB 4.0 adds multi-document ACID; Neo4j offers ACID in graphs), and finally apply the CAP filter to pick a model and product (document → MongoDB, key‑value → Redis, wide‑column → Cassandra/DynamoDB, graph → Neo4j/JanusGraph). Anecdote: NoSQL concepts predate the 2000s surge; Slides.com downtime illustrates availability vs consistency tradeoffs.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 6:20NoSQL vs Relational Databases
- 8:08Cap Theorem
- 14:17Two Options
- 15:00Network Reliability
- 17:20Availability
- 19:28Why I used Slidescom
- 20:07Acid vs Base Properties
- 21:01Consistency Models
- 22:26Base Properties
- 23:49The ThreeStep Guide
- 24:30The Four Characteristics of Your Data
- 25:35Data Volume
- 26:53Data Velocity
- 29:20Data Variety
- 31:04Data Valence
- 36:05Acid vs Base
- 43:56Outro
related talks
42mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
01h 00mFrom Relational Databases to NoSQL
38mNoSQL Databases: Its not a free lunch
01h 01mNoSQL: An Analysis
45mNoSQL: Death to Relational Databases
43mThe State of NoSQL in 2021
42mMyths of NoSQL
45mDemystifying NoSQL: The SQL developer's guide