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

Taught in

References