Relational or Non-Relational? Choosing the Best Database for the Task
summary
Clear rule set: use relational when you need strict ACID transactions and normalized data; avoid relational for logs, images, large text or BLOBs and instead write to files or object storage. Use Azure Cosmos DB for document or massive scale needs — example: a URL redirect document implementation works and is simple to change. Key design facts: pick partition keys to avoid the 20 GB physical partition limit and fan‑out queries, and choose among Cosmos DB’s five consistency models to trade latency for consistency.
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
55mSQL Server vs Azure Cosmos DB
42mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
54mSay Yes to NoSQL for the .NET SQL Developer
18mNoSQL, YesCosmos: Build that Eventually Consistent Application using Azure Cosmos DB