Myths of NoSQL
summary
Examines common arguments for using NoSQL databases, discusses consequences of lacking ACID transactions, and analyzes the impact of the CAP theorem. Covers NoSQL as an alternative to relational databases and the trade-offs around consistency, availability, and partition tolerance.
AI-written summary · about
chapters (29)
- 0:00NoSQL intro
- 1:05What NoSQL is
- 3:42Query language vs DB choice
- 5:35SQL modeling issues
- 7:25Specialization vs performance
- 8:52NoSQL myths
- 9:56Easy install
- 11:22Clusters as key
- 12:27Fashion vs needs
- 13:32NoSQL vs SQL
- 15:21When to use NoSQL
- 16:02Costs of distributed DBs
- 18:18No transactions in distributed systems
- 20:10CAP theorem basics
- 21:14Consistency vs availability
- 22:42Why consistency matters
- 25:51Inconsistency consequences
- 27:21Cluster config impact
- 29:23Key DB features
- 30:10Choosing by needs
- 32:06Cassandra at Allegro
- 35:00Ensuring consistency
- 36:29Big data problems
- 37:34Elasticsearch limits
- 38:42Tech vs consistency
- 40:06Was Cassandra right?
- 41:06PostgreSQL JSON
- 41:57Avoid bad DB choices
- 42:19Summary & Q&A
related talks
01h 01mNoSQL: An Analysis
45mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
38mNoSQL Databases: Its not a free lunch
01mDon't Drop ACID - Transactions in Distributed NoSQL
01h 00mFrom Relational Databases to NoSQL
45mDemystifying NoSQL: The SQL developer's guide
45mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
42mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
