Rightsizing vs Autoscaling
People think autoscaling makes a server the right size, and it does not. Autoscaling adds or removes copies of a server as traffic changes. Each copy stays the same size. Rightsizing changes the size itself, to fit the work one server really does. A team often needs both: the right size, and the right number.
Rightsizing
Matching each cloud server's size to the work it really does. Most end up smaller.
Rightsizing means changing a cloud server to the size its work really needs. Many servers are picked too big, just in case, and then sit mostly idle. You look at how much processor and memory each one really uses. Then you move it to a smaller size, or a bigger one if it struggles. Most clouds give advice on which servers to resize. It is often the first saving a team makes.
Autoscaling
More servers when busy, fewer when quiet. It happens on its own.
Autoscaling adds or removes servers on its own as the load changes. You set a rule, such as keeping the average processor use near 50 percent. When traffic rises, it starts new instances from a machine image. When traffic falls, it shuts some down. A load balancer spreads the work across whatever is running.
In one line
- Rightsizing
- Matching each cloud server's size to the work it really does. Most end up smaller.
- Autoscaling
- More servers when busy, fewer when quiet. It happens on its own.