Say YES! to NoSQL: A Guide on When to Ditch Relational Databases
summary
Three-step decision framework: first evaluate the data by four characteristics — volume velocity variety valence — and prefer NoSQL when those are high; next decide whether ACID or BASE properties matter (MongoDB 4.0 supports multi-document ACID, Neo4j offers ACID graphs); finally apply the CAP tradeoffs to pick a data model and engine. Covers the four data models document, key-value, wide-column, graph with concrete examples (MongoDB, Redis, RocksDB, Apache Ignite, Cassandra, Neo4j, JanusGraph, CouchDB, DynamoDB) and pragmatic tradeoffs.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:49What is NoSQL
- 2:32History of NoSQL
- 3:35Data Models
- 6:21NoSQL vs Relational Databases
- 8:10Cap Theorem
- 9:02Consistency
- 11:10Availability
- 13:43Caps Theorem
- 16:20Partition tolerant consistent systems
- 20:08ACID vs BASE properties
- 23:50The 3step guide to ditching relational databases
- 24:32The 4 characteristics of your data
- 26:55Data velocity
- 29:21Data variety
- 31:06Data valence
- 36:07Acid
- 42:36Conclusion
related talks
42mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
38mNoSQL Databases: Its not a free lunch
01h 00mFrom Relational Databases to NoSQL
01h 01mNoSQL: An Analysis
19mRelational or Non-Relational? Choosing the Best Database for the Task
45mNoSQL: Death to Relational Databases
37mHow to Choose the Right Database for Your Project: A Guide Between SQL and NoSQL
45mDemystifying NoSQL: The SQL developer's guide