In short
- Definition: The ability of a system to automatically add or remove resources to match changes in workload.
- Goal: Absorb demand peaks without over-provisioning resources during quiet periods.
- Example S.M.A.R.T. requirement: Capacity doubled within 5 minutes of a load spike, and released within 15 minutes after it ends.
1. Definition
As a non-functional requirement, elasticity describes the ability of a system to add or remove resources automatically so that capacity follows the workload [1], [2], [3].
Elasticity has two directions. Scaling down matters as much as scaling up.Key takeaway
Elasticity is typical of cloud platforms: instances, containers or serverless functions are added when traffic rises and released when it falls. It requires stateless components, automatic scaling rules and fast start-up.
Elasticity differs from scalability. Scalability is the ability to grow; elasticity is the ability to grow and shrink automatically and quickly.
2. Goal
The goal is to absorb demand peaks without paying for idle capacity during quiet periods.
Without elasticity, teams over-provision for the peak all year, or under-provision and suffer slowdowns when traffic surges.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Scale-out time | Minutes from load spike to added capacity | < 5 min | Load test with a sudden spike |
| Scale-in time | Minutes after load returns to normal | < 15 min | Monitoring of instance counts |
| Over-provisioning | % unused capacity outside peaks | < 30% | Utilization metrics |
| Errors during scaling | % of failed requests | < 0.1% | Load test results |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Web platform: “When traffic doubles within 5 minutes, the platform shall add capacity automatically within 5 minutes, with fewer than 0.1% failed requests.”
- Cost control: “Within 15 minutes after a peak ends, unused instances shall be released automatically.”
- Events: “The ticketing API shall scale from 2 to 40 instances during a sales opening without manual intervention.”
5. Questions to Ask Stakeholders
- How variable is the load: daily cycles, seasonal peaks, sudden events?
- How fast does traffic rise during a peak?
- Which components can scale automatically, and which cannot (databases, licenses)?
- What are the minimum and maximum capacity limits?
- How much can the business spend at peak?
- How will scaling rules be tested?
6. Common Pitfalls
- Scaling only the web tier. The database or a third-party API may become the bottleneck.
- Slow start-up. If instances take minutes to start, scaling arrives after the peak.
- No upper limit. Unbounded scaling can produce a huge bill after a bug or an attack.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Scalability — the ability to grow; elasticity adds automatic growth and shrinkage.
- Capacity — elasticity adjusts available capacity in real time.
- Cost — releasing unused resources saves money.
- Boot Up Time — fast start-up makes scaling effective.
8. FAQ
Scalability is the ability to handle more load by adding resources; elasticity is doing that automatically, in both directions, as load changes.
Some managed databases can scale automatically, but many need planned capacity. Check each component.
Run load tests with sudden spikes and drops, and measure how fast capacity follows and how many requests fail.
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. |
|---|---|---|---|
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [4] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| API | Application programming interface | Defined way for one program to request data or services from another. | [5] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [6] |
| 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. | [3] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Cloud | Computing resources (servers, storage, services) rented over the internet from a provider. | [7] |
| Container | Package that bundles an application with everything it needs to run, isolated from other software. | [8] |
| Database | Organized store of data that software can query and update. | [9] |
| Load test | Test that simulates the expected number of users or requests to check how the system behaves. | [10] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [11] |
10. Sources and Further Reading
- [1] “Elasticity (computing).” Wikipedia. https://en.wikipedia.org/wiki/Elasticity_(computing) (accessed Nov. 18, 2026).
- [2] “Autoscaling.” Wikipedia. https://en.wikipedia.org/wiki/Autoscaling (accessed Nov. 18, 2026).
- [3] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [4] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [5] “API.” Wikipedia. https://en.wikipedia.org/wiki/API (accessed Nov. 19, 2026).
- [6] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [7] “Cloud computing.” Wikipedia. https://en.wikipedia.org/wiki/Cloud_computing (accessed Nov. 19, 2026).
- [8] “Containerization (computing).” Wikipedia. https://en.wikipedia.org/wiki/Containerization_(computing) (accessed Nov. 19, 2026).
- [9] “Database.” Wikipedia. https://en.wikipedia.org/wiki/Database (accessed Nov. 19, 2026).
- [10] “Load testing.” Wikipedia. https://en.wikipedia.org/wiki/Load_testing (accessed Nov. 19, 2026).
- [11] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @johnmcclane; inline photo by @kierinsightarchives, both on Unsplash.








