In short
- Definition: The ability of a system to handle growing workload by adding resources, either more machines (horizontal) or more powerful ones (vertical).
- Goal: Support growth without redesign or loss of performance.
- Example S.M.A.R.T. requirement: Throughput growing at least 80% linearly up to 10 nodes, while response time stays within target.
1. Definition
As a non-functional requirement, scalability describes the ability of a system to handle a growing workload by adding resources, either more machines (horizontal scaling) or more powerful ones (vertical scaling) [1], [2].
A system scales only as far as its least scalable component.Key takeaway
In ISO/IEC 25010:2023, scalability appears as a sub-characteristic of flexibility [3]. A scalable system keeps meeting its performance targets as users, data and transactions grow, at a cost that grows reasonably.
Scalability is limited by the parts that cannot be multiplied easily: a single database, shared locks, a licensed component or a partner API.
2. Goal
The goal is to support growth without redesign or loss of performance.
Systems that do not scale hit a wall during growth or success, often at the worst time, and need urgent rework.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Scaling efficiency | % of linear throughput gain per added node | ≥ 80% up to the target size | Load tests at increasing cluster sizes |
| Response time as load grows | Seconds at the 95th percentile | Within target up to 10× today’s load | Load test |
| Maximum tested scale | Users or transactions | ≥ 3× the 2-year forecast | Load test report |
| Cost per transaction at scale | Currency | Stable or decreasing | Cost and volume data |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Horizontal scaling: “Throughput shall grow at least 80% linearly when adding nodes up to 10 nodes, while response time stays within target.”
- Growth: “The platform shall support 10 times today’s number of users without architectural change, demonstrated by a load test before each yearly planning cycle.”
- Data: “The search service shall keep response times under 500 ms with 100 million indexed documents.”
5. Questions to Ask Stakeholders
- How much growth is expected, and over what period?
- Which dimension grows: users, data, transactions, tenants?
- Which components are hard to scale?
- Is horizontal scaling possible, or only vertical?
- How does cost grow with scale?
- How will scalability be tested?
6. Common Pitfalls
- Stateful services. Session data in memory blocks horizontal scaling. Externalize state.
- The single database. It often becomes the bottleneck. Plan read replicas, partitioning or caching.
- Testing only today’s load. Scalability needs tests well beyond current volumes.
7. Related NFRs
- Capacity — the current maximum load.
- Elasticity — automatic scaling up and down.
- Performance — must hold as load grows.
- Throughput — grows with scale if the design allows it.
- Cost — scaling should keep unit costs reasonable.
8. FAQ
Horizontal scaling adds more machines; vertical scaling makes existing machines more powerful.
Scalability is the ability to grow; elasticity is growing and shrinking automatically with demand.
Run load tests at increasing levels and cluster sizes, and check that throughput grows and response times stay within targets.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| ISO | International Organization for Standardization | Independent international body that publishes standards, such as ISO/IEC 25010 for software quality. Its short name comes from the Greek “isos” (equal) and is said as a word. | [4] |
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [5] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| API | Application programming interface | Defined way for one program to request data or services from another. | [6] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [7] |
| IEC | International Electrotechnical Commission | International standards body for electrical and electronic technologies; it publishes joint “ISO/IEC” standards with ISO. | [8] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [2] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Cache | Fast temporary storage of frequently used data to avoid recomputing or refetching it. | [9] |
| Database | Organized store of data that software can query and update. | [10] |
| Horizontal and vertical scaling | Adding more machines (horizontal) or making one machine more powerful (vertical). | [1] |
| Load test | Test that simulates the expected number of users or requests to check how the system behaves. | [11] |
| Percentile | Value below which a given share of measurements falls; “95th percentile under 300 ms” means 95% of requests are faster than 300 ms. | [12] |
| Replication | Keeping synchronized copies of data or services on several machines. | [13] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [14] |
| Throughput | Amount of work a system completes per unit of time, such as requests per second. | [15] |
| Transaction | Unit of work, such as a payment or an order, that must complete fully or not at all. | [16] |
10. Sources and Further Reading
- [1] “Scalability.” Wikipedia. https://en.wikipedia.org/wiki/Scalability (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “ISO/IEC 25010 product quality model.” ISO 25000. https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 (accessed Nov. 18, 2026).
- [4] “International Organization for Standardization.” Wikipedia. https://en.wikipedia.org/wiki/International_Organization_for_Standardization (accessed Nov. 19, 2026).
- [5] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [6] “API.” Wikipedia. https://en.wikipedia.org/wiki/API (accessed Nov. 19, 2026).
- [7] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [8] “International Electrotechnical Commission.” Wikipedia. https://en.wikipedia.org/wiki/International_Electrotechnical_Commission (accessed Nov. 19, 2026).
- [9] “Cache (computing).” Wikipedia. https://en.wikipedia.org/wiki/Cache_(computing) (accessed Nov. 19, 2026).
- [10] “Database.” Wikipedia. https://en.wikipedia.org/wiki/Database (accessed Nov. 19, 2026).
- [11] “Load testing.” Wikipedia. https://en.wikipedia.org/wiki/Load_testing (accessed Nov. 19, 2026).
- [12] “Percentile.” Wikipedia. https://en.wikipedia.org/wiki/Percentile (accessed Nov. 19, 2026).
- [13] “Replication (computing).” Wikipedia. https://en.wikipedia.org/wiki/Replication_(computing) (accessed Nov. 19, 2026).
- [14] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [15] “Network throughput.” Wikipedia. https://en.wikipedia.org/wiki/Network_throughput (accessed Nov. 19, 2026).
- [16] “Database transaction.” Wikipedia. https://en.wikipedia.org/wiki/Database_transaction (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @youssef00; inline photo by @borkography, both on Unsplash.




