NoSQL: Death to Relational Databases
summary
Argues that NoSQL isn’t a slogan but tradeoffs: shows memory-bound Redis crash from a Rails Rumble deployment, demonstrates Cassandra’s eventual consistency and quorum reads, compares CouchDB (HTTP JSON views, no partial updates) with MongoDB (documents, easy updates) and Tokyo Cabinet’s toolchain, models comic-book and Avengers data in column, document and key stores, and builds a Neo4j graph for relationship queries to show graph shortest-path fast and when each system actually simplifies or complicates work.
AI-written summary · about
chapters (25)
- 0:00Start
- 1:34Motivations
- 9:56Taxonomy
- 10:20Key-Value Stores
- 11:35Column-Oriented Stores
- 13:00Document-Oriented Stores
- 14:27Graph Databases
- 14:48graph theory
- 16:47Performance
- 18:02Scalability
- 19:12Flexibility
- 20:45Domain Complexity
- 24:29Data Types strings tables!
- 29:58Web-Inspired JSON storage HTTP/RESTful interface
- 32:55Storage binary JSON documents
- 33:28Queries dynamic index-based
- 38:19Simulations
- 39:00Lack of Structure
- 40:27Logging
- 40:38Hybrid Domains
- 41:29different scales
- 42:01Next Steps
- 42:48Ignore the Database
- 43:10Change the Default
- 43:40Application Templates start with something new
related talks
01h 01mNoSQL: An Analysis
01h 00mFrom Relational Databases to NoSQL
38mNoSQL Databases: Its not a free lunch
38mNot all data is created equal: NoSQL
45mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
45mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
34mData Storage: NoSQL Toasters and a Cloud of Kitchen Sinks
42mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases