Not all data is created equal: NoSQL
summary
Argues that running self‑hosted NoSQL is a bad bet and urges managed cloud services instead, citing an exposed MongoDB dataset affecting 66 million users and millions of unprotected instances; explains concrete tradeoffs — JSON document storage for denormalized reads, scaling by adding nodes, CAP choices that force consistency vs availability decisions — and gives tool-specific guidance (MongoDB, Redis, Neo4j, Cassandra) and cloud options like Azure CosmosDB and DynamoDB with criteria: security, latency, availability, global distribution, and TCO.
AI-written summary · about
chapters (12)
- 0:00Intro
- 11:00Cap Theorem
- 17:59Three Vs
- 24:37KeyValue Databases
- 25:57Cloud Databases
- 29:29MongoDB
- 31:42Cloudbased hosting
- 33:10Consistency
- 34:38Latency
- 35:12Availability
- 36:02Global Distribution
- 36:22Total Cost of Ownership
related talks
45mNoSQL: Death to Relational Databases
01h 01mNoSQL: An Analysis
01h 00mFrom Relational Databases to NoSQL
34mData Storage: NoSQL Toasters and a Cloud of Kitchen Sinks
45mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
38mNoSQL Databases: Its not a free lunch
45mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
54mNoSQL Shouldn’t Mean NoSecurity
