read to write ratio
How many reads a system serves for every write, such as fifteen reads to one write.
In more detail
The ratio is a design instruction. A read heavy system benefits from caches and read replicas; a write heavy one needs partitioning and batching and gets little from a cache. Deciding whether to fan out on write or on read answers the same question.
Related terms
- cache — A store of earlier answers kept close to where they are needed so they can be reused instead of fetched or computed again.
- read replica — A copy of a database that follows the primary’s changes and can serve read traffic or be promoted to take over.
- partitioning — Splitting a dataset into separate pieces, each owned by a different machine or process, so the work can spread out.
- fan out on write — Copying a new message into every recipient's feed or inbox at the moment it is written.
Taught in
- What A Design Is For, And How To Run A Design Discussion — Scalable System Design & Distributed Architecture
- Requirements: The Constraints That Shape The System — Scalable System Design & Distributed Architecture
- Back Of The Envelope Estimation: Traffic And Throughput — Scalable System Design & Distributed Architecture
- Worked Design Three: A Metrics Ingestion Pipeline — Scalable System Design & Distributed Architecture