Infrastructure / DevOps

Vertical vs horizontal scaling: what's the difference?

Vertical vs horizontal scaling explained: when to make one server bigger, when to add servers behind a load balancer, and what each means for cost and uptime.

  • 8 min read
  • 5 questions
  • +35 XP
Transcript

Horizontal vs Vertical Scaling, explained by cats. Kitty sells fish online. Kitty’s store gets popular. More cats visit. The server starts to struggle. Kitty needs more power. Kitty has two options. Option 1, Vertical scaling. This means. Kitty make one server bigger.

More CPU. More memory. More tuna for cats. Easy to do. But there’s a limit. One server can only get so big. And if it breaks. everything goes down. Option 2: Horizontal scaling. It means, Kitty add more servers. More helping paws.

Traffic gets shared. If one server naps, others keep working. But it's A little harder to set up. Needs load balancers. and a lot of coordination. But it's good for scaling tuna stores. Both add power. Just different ways. Smart systems use both. scale vertically first, then scale horizontally when the tuna rush hits.