Part 1 of 6 · 1 min read
Why this page comes first
In this module you will
- Explain the get-and-put access model a key-value store offers.
- Explain why looking up a key needs an index, and what happens without one.
- Explain why a key-value model partitions easily across many machines.
- State what a key-value store gives up compared to a relational table or a document store.
- Distinguish a durable key-value store from a caching-only one.
The last page covered the document model. A document store still lets an application query by fields inside a document. A key-value store strips that down further. It supports exactly two operations: store a value under a key, and fetch a value by that same key. This page explains why that narrower model is useful, and what it costs.