You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode Message queues: how a website takes a flood of slow jobs without slowing down

What happens when a website goes viral: how a site keeps up with millions of visitors

Autoscaling: why adding servers by itself can still come too late

A website gets a big crowd in the morning and a small one at night. You pay for every server by the hour, even when it does nothing. Autoscaling adds and removes servers by itself. But a crowd can grow faster than autoscaling can follow.

  1. 1 A few hundred players are left at night, and two servers would be plenty. But you cannot sit up all night switching servers off, then all morning switching them back on.3:00youEverynight?

    A few hundred players are left at night, and two servers would be plenty. But you cannot sit up all night switching servers off, then all morning switching them back on.

  2. 2 The crowd comes and goes in waves: big at 9:00, small at night, bigger again whenever Rono posts. You want the number of servers to follow the waves on its own.players9:003:00

    The crowd comes and goes in waves: big at 9:00, small at night, bigger again whenever Rono posts. You want the number of servers to follow the waves on its own.

The rest of this episode is for subscribers

Subscribe to read every premium episode. You can cancel when you want.

Paid yearly: $99 instead of $119.88

Next episode Load shedding and rate limiting: why turning some visitors away keeps a website up for the rest

Share this comic

More comics