Design Microservices Architecture with Patterns and Principles - Scalability - Vertical Scaling - Horizontal Scaling

The video tutorial explains scalability, which is the ability of an application to handle increasing numbers of requests. It discusses the importance of scaling resources to prevent downtime and reduce latency. The tutorial differentiates between horizontal scaling, which involves adding more machines, and vertical scaling, which involves adding more power to existing machines. It highlights the implementation and performance differences between the two approaches and concludes with a brief introduction to further explanations of vertical and horizontal scaling.

What is scalability primarily measured by?

• The number of requests an application can handle simultaneously

• The number of users an application can support

• The speed of the application's response time

• The amount of data an application can store

Which of the following best describes horizontal scaling?

• Adding more machines to a resource pool

• Increasing the speed of a single machine

• Adding more power to an existing machine

• Reducing the number of machines in use

What is a key characteristic of vertical scaling?

• It is described as scaling out

• It involves adding more machines

• It requires changing the application logic

• It involves adding more power to an existing machine

What is a fundamental requirement for horizontal scaling?

• Breaking logic into smaller pieces for parallel execution

• Running the same code on lower-spec machines

• Increasing the CPU and RAM of a single machine

• Reducing the number of requests handled

Why is vertical scaling often considered easier?

• It reduces the need for additional resources

• It requires no changes to the application logic

• It involves adding more machines

• It simplifies the application code