Relational or Non-Relational? Choosing the Best Database for the Task
summary
Compares relational ACID tradeoffs with NoSQL BASE and shows concrete choices: uses Azure Cosmos DB document model to build a URL redirection service (zombocom redirect) with a userID partition key, explains physical partitions limited to 20 GB and automatic splits, and highlights five consistency modes to pick between latency and correctness. Recommends avoiding relational storage for logs, images, or huge text, and favors document stores for schema‑less, large scaleout workloads where single‑record reads dominate.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:00Database models defined
- 3:15Relational normal forms
- 5:58NoSQL database design
- 7:53Partitioning in Cosmos DB
- 10:15Consistency and CAP theorem
- 14:01Choosing the right database
- 18:17Conclusion
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
42mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
45mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
45mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases