liveBook · Manning

Vertical scaling

As explained in Building Web APIs with ASP.NET Core

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

Vertical scaling, or scale-up, increases the processing power of a single server or database node. It handles greater workload capacity by strengthening one machine rather than adding nodes. section 4.1.1

Compare vertical scaling with horizontal scaling when choosing a database architecture:

  • Horizontal scaling, or scale-out, adds nodes to a cluster and distributes workload across multiple servers. section 4.1.1
  • A single-node design can create a single point of failure, while clustered systems can improve availability through multiple nodes. section 4.1.1
  • Modern cloud SQL and hybrid database services can reduce the cost of scaling up and add clustering or redundancy to mitigate its risks. section 4.1.1

How Building Web APIs with ASP.NET Core covers it

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.
How it connects
Connects vertical scaling with horizontal scaling, database servers, distributed systems, clustering, redundancy, and availability.

Also explained in

Compare how 7 books explain vertical scaling →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Building Web APIs with ASP.NET Core. The section links point to the parts of the book it draws on.