Level 11 of 13 · about 1 week
NoSQL and alternative data models
Document databases, key-value stores, graph databases and column-family stores as four different ways to model the same data, each suited to a different access pattern, and how to pick a model for a real workload rather than a trend.
Modules
Core: everyone needs it. Common: most jobs use it. Specialist: optional depth, safe to skip on a first read.
1
Document databases
storing a record as one self-contained tree instead of spreading it across tables, and where that stops paying off
Core 6 parts · about 2 hours
2
Key-value stores
the simplest access model there is, get and put by a single key, and why that simplicity scales so well
Core 6 parts · about 2 hours
3
Graph databases
vertices and edges for data that is mostly about its own connections, and the query style that follows from it
Specialist 5 parts · about 2 hours
4
Column-family stores
rows with flexible, grouped columns instead of a fixed set, built on the write path covered back in Level 5
Specialist 5 parts · about 2 hours
5
Picking a data model for a real workload
matching each part of a real system to the model that fits its own access pattern, and running more than one model at once
Core 5 parts · about 2 hours