liveBook · Manning

Vertical scaling

Also called scaling up, vertical scalability

Vertical scaling increases or decreases a system’s capacity by changing the resources available to an existing machine, node, or instance.

How 10 Manning books explain it

Acing the Frontend Interview

Vertical scaling increases the compute, memory, storage, or other resources of a single machine.

How it is used
Frames vertical scaling as an interview-ready strategy for increasing capacity on a single machine.
How deep it goes
Defines resource increases, trade-offs, and selection guidance while emphasizing comparison rather than implementation details.
Examples
Uses a server upgrade from 2 CPUs and 4 GB RAM to 8 CPUs and 32 GB RAM.
What you can do after
Evaluate scaling choices by weighing simplicity, growth limits, downtime, fault tolerance, and business constraints.

Read how Acing the Frontend Interview explains vertical scaling →

Elasticsearch in Action, Second Edition

Vertical scaling increases system capacity by increasing the resources of existing machines, such as memory or CPU capacity.

How it is used
Handles Elasticsearch capacity growth by enlarging existing machines when data or query load increases.
How deep it goes
Explains resource increases, same-machine nodes, downtime, and failure concentration, but stops short of a step-by-step upgrade procedure.
Examples
Uses five 2-TB servers to meet a 10-TB requirement across five indexes and discusses additional nodes on one machine.
What you can do after
Evaluate capacity strategies while anticipating maintenance downtime and the risks of concentrating data on one machine.

Read how Elasticsearch in Action, Second Edition explains vertical scaling →

Building Web APIs with ASP.NET Core

Vertical scaling is increasing the processing capacity of a single server or node.

How it is used
Frames database capacity planning as a choice between strengthening one node and distributing workload across a cluster.
How deep it goes
Defines scale-up and contrasts it with scale-out, but stops short of implementation procedures or capacity calculations.
Examples
Uses SQL, NoSQL, cloud-based SQL, and hybrid database services as architectural comparison points.
What you can do after
Evaluate database architectures by comparing single-node capacity, cluster complexity, cost, and availability trade-offs.

Read how Building Web APIs with ASP.NET Core explains vertical scaling →

Refactoring to Rust

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

How it is used
Addresses performance limits by increasing the resources available to an existing machine instance.
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 you can do after
Evaluate vertical scaling as an alternative to rewriting code or adding system instances.

Read how Refactoring to Rust explains vertical scaling →

ActiveMQ in Action

Vertical scalability is the ability to increase a system's capacity by adding resources to an existing node.

How it is used
Uses broker tuning to increase the connection capacity of a single ActiveMQ broker.
How deep it goes
Explains thread usage and gives configuration guidance for transport I/O, dispatch threads, memory, and encoding.
Examples
Uses NIO, a task-runner property, memory limits, and OpenWire encoding as concrete tuning examples.
What you can do after
Configure an ActiveMQ broker for more concurrent connections by tuning transport I/O, dispatch threads, memory, and OpenWire encoding.

Read how ActiveMQ in Action explains vertical scaling →

Microsoft Azure in Action

A scaling technique that changes the size of an individual virtual machine or database server to increase or decrease its computing resources.

How it is used
Adjusts one VM or database server to match changing application demand and control resource spending.
How deep it goes
Defines scaling up and down, contrasts scaling out, and demonstrates Azure SQL sizing without detailing internals.
Examples
Uses changing Azure VM sizes, seasonal Banning Books traffic, DTU tiers, and an Azure CLI database update.
What you can do after
Operate Azure VMs or SQL databases by selecting larger or smaller resource configurations for changing workloads.

Read how Microsoft Azure in Action explains vertical scaling →

Grokking Software Architecture

Increasing the capacity of a single system instance by adding resources such as processing power, memory, or storage.

How it is used
Handles increased load by making one existing server more powerful.
How deep it goes
Defines the server upgrade and explains its ease, physical ceiling, and failure risk, without detailing implementation steps.
Examples
Uses a coffee-shop barista analogy and a cloud virtual-machine upgrade with specific monthly costs and resources.
What you can do after
Operate a virtual machine by upgrading its resources, usually without changing application code.

Read how Grokking Software Architecture explains vertical scaling →

Machine Learning System Design

A scaling technique that increases the capacity of a single machine by upgrading or replacing its hardware.

How it is used
Supports training pipelines when a dataset or workload exceeds current machine capacity.
How deep it goes
Defines hardware upgrades, explains simplicity and limits, and stops short of detailed implementation procedures.
Examples
Uses doubled or quadrupled RAM, upgraded GPUs, cloud compute resources, and a single training machine as examples.
What you can do after
Evaluate whether hardware upgrades can meet training demands before adopting distributed scaling.

Read how Machine Learning System Design explains vertical scaling →

Cloud Observability in Action

Vertical scaling is the practice of increasing the resources of an existing system instance, such as memory or storage.

How it is used
Supports changing compute or telemetry load by increasing resources on an existing instance.
How deep it goes
Defines the scaling direction and gives Prometheus limits, but defers detailed implementation procedures.
Examples
Uses serverless VMs with adjusted CPU or RAM and Prometheus with added RAM or persistent storage.
What you can do after
Operate/configure an existing compute or Prometheus instance with greater CPU, RAM, or storage capacity.

Read how Cloud Observability in Action explains vertical scaling →

Grokking Concurrency

Vertical scaling increases system performance by adding capacity to existing processing resources or replacing them with more powerful resources.

How it is used
Explains how systems improve performance by upgrading existing processing resources before considering distributed alternatives.
How deep it goes
Defines hardware upgrades, performance ceilings, and costs, then contrasts them with horizontal scaling without detailing implementation.
Examples
Uses more memory, a more powerful processor, a supercomputer, and top-tier cloud instances as upgrade examples.
What you can do after
Evaluate whether upgrading one machine can improve performance before choosing distributed processing resources.

Read how Grokking Concurrency explains vertical scaling →

Also covered in

What to know first

Related concepts

Questions about vertical scaling

What is vertical scaling?

Vertical scaling increases or decreases a system’s capacity by changing the resources available to an existing machine, node, or instance.

Which Manning books explain vertical scaling?

Acing the Frontend Interview, Elasticsearch in Action, Second Edition, Building Web APIs with ASP.NET Core, Refactoring to Rust, ActiveMQ in Action, Microsoft Azure in Action, Grokking Software Architecture, Machine Learning System Design and 2 more.

What should I know before learning vertical scaling?

Manning books that teach vertical scaling usually introduce CPU, performance, horizontal scaling and scalability first.

What is the difference between vertical scaling and horizontal scaling?

Vertical scaling increases or decreases a system’s capacity by changing the resources available to an existing machine, node, or instance. Horizontal scaling is increasing or decreasing system capacity by adding or removing computing nodes or service instances that share the workload.

What is vertical scaling a kind of?

Vertical scaling is a kind of autoscaling. Autoscaling is the automatic adjustment of computing resources or service capacity in response to workload demand or system conditions.

What is vertical scaling also called?

Vertical scaling is also called scaling up or vertical scalability.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.