non-functional requirement
A measurable promise about how well a system works, such as how fast, how available, or how durable it must be.
In more detail
The course uses six: a latency target stated at a percentile, an availability target, durability, consistency, the read to write ratio with growth, and a cost ceiling. Each one rules out whole families of design, which is why they are agreed before anything is drawn. An unwritten one tends to surface later as an incident with no owner.
Related terms
- functional requirement — Something a system must let a user do, written as a verb, such as post a message or upload a photograph.
- latency — The time between asking for something and getting the answer back.
- availability — The share of time, or of requests, in which a service works for the people who need it, often written as a percentage such as 99.9 per cent.
- durability — The likelihood that stored data survives hardware failures without being lost, usually stated as a percentage per year.
- consistency — The guarantee about whether what you read reflects what was most recently written.
- read to write ratio — How many reads a system serves for every write, such as fifteen reads to one write.
Taught in
- Requirements: The Constraints That Shape The System — Scalable System Design & Distributed Architecture
- Worked Design One: Ticket Booking, Correctness First — Scalable System Design & Distributed Architecture