Scale LineLesson
Autoscaling that keeps up
Let the fleet grow and shrink with traffic — but new instances arrive late, so keep a minimum with headroom, leave a margin between the thresholds, and autoscale only stateless tiers.
12 minMediumStation: AutoscalingMembers lesson
Membership isn’t open yet. The free lessons are open — 16 of them, including the whole first leg of the Scale Line.
- Users
- Web API
What you'll be able to do
- 1Predict the instance count over a traffic curve, given the thresholds and the time a new instance takes to start.
- 2Explain why autoscaling reacts late to a sudden spike, and how a minimum and headroom cover the gap.
- 3Choose the scaling metric and thresholds — CPU, response time or queue length — and which tiers can autoscale at all.
Inside the lesson
- steps
- 9
- questions
- 10
- simulations
- 2
You guess first, then run the system and see if you were right.
Step 1 · The setup
Pixel's traffic climbs every evening and falls away at night. Its web tier is sized for the evening peak — four large instances, all day long.
Watch a day go by — squeezed into two minutes — and follow the CPU bar.
Steps 2–9 are for members
More on the Scale Line
- Latency & percentilesOpen8 min
- Server capacity & scaling upFree with an account10 min
- Split app and database tiersFree with an account10 min
- Load balancerFree with an account10 min
- Horizontal scaling with a stateless tierFree with an account10 min
- Cache-asideFree with an account10 min
- Object storage for user filesMembers10 min
- A CDN for the files everyone wantsMembers12 min