Relational or Non-Relational? Choosing the Best Database for the Task
summary
Compares relational vs non-relational with concrete rules: a redirect service is implemented in Azure Cosmos DB using the document model and userId partition key and it works at scale; Cosmos enforces logical partitions that map to physical shards with a 20 GB partition limit and offers five consistency models to trade consistency for availability; recommends avoiding relational storage for logs, images, or huge text blobs, and using NoSQL for schema‑flexible, massive scale‑out use cases.
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
55mSQL Server vs Azure Cosmos DB
01h 00mFrom Relational Databases to NoSQL
11mRationale for Relational
42mChoosing the right database