Vertical scaling

As explained in Refactoring to Rust

Vertical scaling is increasing the computational resources available to an existing machine or system instance.

When a system reaches a performance limit, vertical scaling increases the resources available to its existing machine instance rather than duplicating the system. section 8.2

Scaling takes two main forms:

• Vertical scaling adds a faster CPU, additional CPU cores, or more memory to the existing machine. section 8.2
• Horizontal scaling adds more instances, such as extra servers or processes, without changing the machine configuration. section 8.2

Adding resources helps only if the application can take advantage of them; reaching a limit may therefore still require code changes. section 8.2

Figure 8.3 Vertical scaling means adding more resources to existing hardware

Visualizes vertical scaling as adding resources to existing hardware. section 8.2

How Refactoring to Rust covers it

How deep it goes

Defines resource-based scaling and contrasts it with horizontal scaling, but does not detail implementation procedures or measurements.

Examples

Uses faster CPUs, additional cores, and additional memory as examples of vertical scaling.

What it assumes

Assumes awareness that bottlenecks can limit system throughput and that applications may need code changes to exploit scaling.

What you can do after

Evaluate vertical scaling as an alternative to rewriting code or adding system instances.

How it connects

Connects vertical scaling with bottlenecks, horizontal scaling, performance limits, and code changes.

liveBookmanning.com

Read Refactoring to Rust on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Elasticsearch in Action, Second EditionVertical scaling increases system capacity by increasing the resources of existing machines, such as memory or CPU capacity.
• 

  liveBookmanning.com
  Building Web APIs with ASP.NET CoreVertical scaling is increasing the processing capacity of a single server or node.
• 

  liveBookmanning.com
  Microsoft Azure in ActionA scaling technique that changes the size of an individual virtual machine or database server to increase or decrease its computing resources.
• 

  liveBookmanning.com
  Machine Learning System DesignA scaling technique that increases the capacity of a single machine by upgrading or replacing its hardware.
• 

  liveBookmanning.com
  Cloud Observability in ActionVertical scaling is the practice of increasing the resources of an existing system instance, such as memory or storage.
• 

  liveBookmanning.com
  Grokking ConcurrencyVertical scaling increases system performance by adding capacity to existing processing resources or replacing them with more powerful resources.

Compare how 7 books explain vertical scaling →

Related concepts

• horizontal scalingalternative to · Horizontal scaling is adjusting system capacity by adding or removing computing nodes or equivalent instances that share or distribute the workload.
• scalabilitycontrasts with · Scalability is the ability of a system, process, or method to accommodate increasing workload, size, or demand while maintaining acceptable operation.
• autoscalingkind of · Autoscaling is the automatic adjustment of computing resource capacity or running instances in response to workload demand or measured system conditions.
• virtual machineconfigures · A virtual machine is a software-based environment that emulates or implements an abstract computer system, providing an interface on which an operating system or programs can execute.
• sequential processingused by · The execution of operations one after another in a defined order, without overlapping their progress.
• Amazon Relational Database Service (RDS)configures · Amazon Relational Database Service is an AWS-managed service for deploying, operating, and scaling relational databases.

This explainer was generated by Manning's knowledge graph from the text of Refactoring to Rust. The section links point to the parts of the book it draws on.