Rationale for Relational
summary
Covers why relational models matter by tracing Codd’s set-theory origin, showing hierarchical designs duplicate rows and cause corruption, and arguing there is no such thing as schema-less — every store has structure. Compares SQL vs NoSQL trade-offs, notes MongoDB borrowing relational features, highlights NewSQL and relational scales (Google Spanner), and lists concrete benefits: ACID consistency, logical/physical separation, built-in query optimization and easier portability between relational systems.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:34Hierarchical vs Relational
- 2:06Whats wrong with hierarchical data models
- 2:51Schemaless database
- 3:20SQL vs NoSQL
- 4:02No SQL Databases
- 4:49No Scale
- 5:09Quiz Question
- 5:40Relational vs Hierarchical
- 6:07Misconceptions
- 6:54Relational Databases
- 7:34Flexible Schemas
- 8:03Sequel Databases
- 8:46Key Benefits
- 10:21New SQL Kits
- 10:46When not to use MongoDB
- 11:12Outro
related talks
01h 00mFrom Relational Databases to NoSQL
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
45mNoSQL: Death to Relational Databases
56mNewSQL: SQL Is Here to Stay- 19mRelational or Non-Relational? Choosing the Best Database for the Task