Scalability
A quality claim says little without a load profile and growth range.
- Load profileLoad profile: Request volume and mix are described.
- ResponseResponse: Quality under increasing load is measured.
- LimitLimit: Capacity and cost limits define the operating point.
Context
Why this is important
Evaluate capacity adaptation against defined quality goals.
Evaluate capacity adaptation against defined quality goals.
Scalability: inspect the decision
The shop example uses the existing shared database and seven modules. Any added service or deployment model is a hypothetical extension. The team expects shop campaign traffic to triple and defines a scalability scenario: at 3× checkout requests per minute, p95 latency stays below its target while payment success remains stable. A load test first identifies the database as a bottleneck even after adding web instances horizontally. Measurement therefore covers the full transaction path and the cost of added capacity.
This is how you read the picture
- Load profile Load profile
- Response Response
- Limit Limit
| Concept | Meaning | Review question |
|---|---|---|
| Load profile | Request volume and mix are described. | Which target values does the load scenario check? |
| Response | Quality under increasing load is measured. | Which details make the quality requirement measurable? |
| Limit | Capacity and cost limits define the operating point. | What limits a passing test? |
Benefits & limitations
Helps if:
- Evaluate capacity adaptation against defined quality goals.
- State growth range, load mix, and quality target measurably.
Boundaries
- Results apply to the measured load and system configuration.
- Scalability describes behavior across a load range; one peak-load value does not show a growth curve.
In practice
- Describe the growth scenario with baseline load, triple checkout rate, response-time limit, and payment-success rate; state the time window and representative cart mix.
- Run the load test across web, database, and payment paths and check whether extra web instances move the measured bottleneck or merely add database load.
- Compare p95 latency, successful payments, and cost with the agreed objective, and document which load level the result actually covers.
Read the detailed explanation
Scalability describes how a system can adapt capacity to changing load and which quality levels it preserves. A useful claim needs a load profile, growth range, and metric such as throughput or latency.
Scalability is a system quality, not a synonym for fast response. Bottlenecks, data state, dependencies, and cost can limit gains; scaling is the concrete capacity change used to address demand.
The shop example uses the existing shared database and seven modules. Any added service or deployment model is a hypothetical extension. The team expects shop campaign traffic to triple and defines a scalability scenario: at 3× checkout requests per minute, p95 latency stays below its target while payment success remains stable. A load test first identifies the database as a bottleneck even after adding web instances horizontally. Measurement therefore covers the full transaction path and the cost of added capacity. performance and skalierung help compare this decision with adjacent concerns.
Check your understanding
Test yourself in three stages
ReadingCheck in the picture
Which target values does the load scenario check?
View the solution with justification
p95 latency and payment success at triple checkout volume.
ApplyingTransferred to a new situation
Which details make the quality requirement measurable?
View the solution with justification
Load mix, volume range, latency percentile, and success rate.
EvaluateWeighing an alternative
What limits a passing test?
View the solution with justification
The tested configuration and load interval.
Ten times more orders
Compare capacity, distribution and bottlenecks in the shared learning example.
Explore scaling in the shopExplore further
Find variants and links to standalone concepts here.
Elasticity
Elasticity describes how quickly and appropriately capacity responds to changing load. It helps with variable demand; scaling time, minimum capacity, and cost must fit the quality objective.