liveBook · Manning

Horizontal scaling

As explained in Building Web APIs with ASP.NET Core

Horizontal scaling increases capacity by adding or removing service instances rather than enlarging one instance.

Horizontal scaling, or scale-out, increases capacity by adding nodes to a cluster instead of increasing the processing power of one server. section 4.1.1

Scaling out distributes workload across multiple servers and supports changing capacity with demand:

  • Add or remove nodes as workload requirements change. section 4.1.1
  • Use multiple servers to avoid relying on a single point of failure. section 4.1.1
  • Recognize that clustering can introduce consistency problems, performance bottlenecks, and added complexity, especially for SQL databases. section 4.1.1

How Building Web APIs with ASP.NET Core covers it

How deep it goes
Defines scale-out through clusters, workload sharing, and node changes, while stopping short of implementation details.
Examples
Uses multiple database servers forming a cluster and adding or removing nodes to accommodate workload requirements.
What you can do after
Evaluate database architectures by comparing scale-out, scale-up, workload distribution, availability, and operational trade-offs.
How it connects
Connects distributed systems, NoSQL databases, SQL databases, clustering, consistency, availability, and vertical scaling.

Also explained in

Compare how 13 books explain horizontal 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.