Relational or Non-Relational? Choosing the Best Database for the Task
summary
Compares relational vs non-relational with concrete rules and examples: shows a working URL-redirect implemented in Azure Cosmos DB, explains partitioning on a user ID, warns of the 20 GB per physical partition hard limit and the cost of fan-out, lists five consistency models Cosmos offers, and gives clear do/don’t guidance — use relational for strict ACID transactions and relational data, use NoSQL for denormalized, schema-flexible, massive scale-out workloads; logs and images belong on a filesystem.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:28Relational vs non-relational
- 1:31Data models and constraints
- 2:34Normal forms
- 6:27NoSQL document design
- 8:52NoSQL partitioning
- 12:43ACID vs BASE
- 14:08CAP and PACELC theorems
- 16:10Avoid relational databases
- 17:58Choose NoSQL databases
related talks
19mRelational or Non-Relational? Choosing the Best Database for the Task
19mRelational or Non-Relational? Choosing the Best Database for the Task- 19mRelational or Non-Relational? Choosing the Best Database for the Task
- 19mRelational or Non-Relational? Choosing the Best Database for the Task
01h 00mFrom Relational Databases to NoSQL
11mRationale for Relational
42mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
55mSQL Server vs Azure Cosmos DB