Part 1 of 5 · 1 min read
Why this page comes first
In this module you will
- State the access-pattern question to ask before picking a data model for a given piece of data.
- Match a described access pattern to the model, relational, document, key-value, graph, or column-family, that fits it best.
- Explain polyglot persistence, and why one real system often uses more than one data model at once.
- Decide a reasonable data-model split for the bookstore as a whole system.
This level covered four alternatives to the relational model, each solving a different problem. This page closes the level by asking the practical question directly: given one real piece of data, with its own access pattern, which model actually fits it? A real system rarely answers this question the same way for every piece of its own data.