Eight Non-Functional Requirements, Each Paired With the Mechanism That Delivers It
Availability, latency, scalability, durability, consistency, modularity, configurability, resiliency: how to state each measurably and what provides it.
On this page
Requirements meetings are full of “it should be fast and reliable”. That is not a requirement, it is a mood. The useful move is to pair each quality with a measurable target and the mechanism that earns it, then notice what each one costs.
The eight, with mechanism and a measurable form
| Quality | Plain meaning | Typical mechanism | Example target |
|---|---|---|---|
| Availability | Usable when needed | Redundant instances behind load balancers, health checks, multi-zone | 99.9% monthly |
| Latency | Time to respond | CDNs, caching, regional placement, efficient queries | p95 under 300 ms |
| Scalability | Handles growth | Stateless services, replication, partitioning | 10x traffic with flat latency |
| Durability | Committed data survives | Transaction logs (write-ahead), replication, backups | No loss of committed writes |
| Consistency | Everyone sees the same data | Chosen model: strong or eventual consistency | Read-your-writes on profile edits |
| Modularity | Parts change independently | Loose coupling, high cohesion, clear interfaces | A change touches one module |
| Configurability | Behaviour changes without code | Configuration as code, feature flags | Config change deploys without a release |
| Resiliency | Recovers from failure | Message queues, retries, circuit breakers, failover | Recovery within 5 minutes |
How each mechanism actually works
Modularity and configurability are the two that live in code and process rather than infrastructure. Modularity comes from loose coupling (modules know little about each other) and high cohesion (each does one job). Configurability comes from keeping settings in version-controlled configuration as code, so behaviour changes without editing core logic.
Redundancy costs money. Caching costs freshness. Eventual consistency costs simplicity of reasoning. Queues cost visibility into when work finishes. Naming the cost next to the mechanism is what turns a diagram into a decision.
Rank them before you design
Qualities conflict, so choose an order for your product.
| System | Rises to the top | Accepted trade |
|---|---|---|
| Payments ledger | Durability, consistency | Higher latency, lower write throughput |
| Social feed | Availability, latency | Stale reads, eventual consistency |
| Internal admin tool | Modularity, configurability | Modest scale, simple infrastructure |
| Video streaming | Availability, scalability | Complex caching and edge layers |
Do
Write each requirement as a number with a window, check it in production with an SLO, and review the ranking when the product changes.
Don't
Ask for “five nines, instant consistency and low cost” in one breath. Those goals contradict, and the design will quietly sacrifice one without telling you which.
Takeaway
Non-functional requirements are where architecture is actually decided. Put a number on each, pick the mechanism that provides it, write down what it costs, and rank them for your product. That is a design conversation. “Make it scalable” is not.
Frequently asked questions
What is a non-functional requirement?
A quality attribute describing how well the system must behave rather than what it does: how available, fast, durable, consistent or maintainable it is. Functional requirements say a user can place an order. Non-functional requirements say it works at 99.9 percent availability within 300 milliseconds.
How do I make a non-functional requirement measurable?
State a number and a window: availability 99.9 percent per month, p95 latency under 300 milliseconds for checkout, recovery point of 5 minutes. A vague word like fast or reliable cannot be tested, monitored or traded off. Service level objectives are the usual way to write them down.
Do all eight qualities matter equally for every system?
No, and they often conflict. Strong consistency costs latency, extreme availability costs money, high configurability costs simplicity. A payments system prioritizes durability and consistency, a social feed prioritizes availability and latency. Rank them for your product before choosing mechanisms.
What is the difference between availability and resiliency?
Availability is the fraction of time the system is usable. Resiliency is its ability to absorb failures and recover: retries, queues, circuit breakers, failover. Resiliency is one way to reach availability, but you can be available simply by being lucky, and resilient yet briefly unavailable during a failover.



/* Comments */
Comments are offline right now — we reconnect automatically, nothing is lost.