workload table
A table listing each entity with its hottest read, write rate, size and the invariant it must keep, used to choose storage.
In more detail
Filling it in exposes mixed needs honestly: checkout needs a transaction, a profile fits a document, search needs its own index. One product can use several stores as long as each fact has one owner.
Related terms
- access pattern — How an application actually reads and writes its data: how often, how much, by which key and how quickly it needs answers.
- invariant — A rule that must always hold for an object or system, such as a count never being negative.
- entity — A thing in an application's domain with its own identity, such as a user, account or product, usually stored in a database.
Taught in
- The Storage Decision: Relational Versus Document — Scalable System Design & Distributed Architecture