What it means
Scaling can be vertical, horizontal, scheduled, or event driven. Elasticity typically relies on automation, stateless or partitionable design, health signals, and capacity limits.
Why it matters
Correct scaling improves availability and efficiency. Poorly controlled scaling can amplify software defects, attacks, configuration mistakes, and cost.
Practical focus
- Choose metrics that reflect real demand
- Define minimum, maximum, and safe growth limits
- Test scale-out and scale-in behavior
- Protect scaling controls from abuse and noisy signals
Common mistakes
- Confusing elasticity with resilience
- Scaling a stateful bottleneck without redesign
- Allowing unbounded automatic growth
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: