Design Microservices Architecture with Patterns and Principles - Vertical Scaling - Scale Up

The video tutorial explains vertical scaling, which involves enhancing a single server's capacity by adding more resources like CPU, RAM, and disk space. It highlights that while vertical scaling allows for increased capacity without changing existing code, it has limitations due to hardware constraints and can become costly. When a single server reaches its maximum capacity, horizontal scaling, or adding more servers, becomes necessary to handle increased requests.

What is the primary goal of vertical scaling?

• To rewrite existing code for better performance

• To strengthen a single node by adding more hardware

• To distribute load across multiple servers

• To reduce the number of servers in a network

Which of the following is NOT a resource typically added during vertical scaling?

• Network Bandwidth

• CPU

• RAM

• Disk

What is a significant limitation of vertical scaling?

• It requires rewriting the entire codebase

• It can only increase up to the server's maximum capacity

• It allows unlimited scalability

• It is cheaper than horizontal scaling

Why might vertical scaling become highly expensive?

• Because it requires multiple servers

• Due to the need for specialized software

• When reaching the maximum capacity of the hardware

• Because it involves complex network configurations

When is horizontal scaling necessary?

• When there is a need to reduce hardware costs

• When a single server can handle all requests

• When vertical scaling is no longer sufficient

• When the existing code needs to be changed