Municipal autoscaling flaps between scale-out and scale-in within minutes, thrashing instance counts. What stability control should ops add?
Select an answer to reveal the explanation.
Short Explanation
Flapping autoscaling is a thermostat that turns the furnace on and off every thirty seconds—exhausting and expensive. Cooldown periods and sensible windows let the system settle before the next move. Stability is part of scaling, not an afterthought.
Full Explanation
Cooldown periods and evaluation windows prevent rapid oscillation between scale-out and scale-in when metrics hover near thresholds. Flapping wastes cost, stresses orchestration, and can harm availability. Cloud+ scaling design includes stability controls so autoscaling remains effective rather than thrashing.