liveBook · Manning

Scalability

As explained in Think Distributed Systems

Scalability is the ability of a system to maintain its intended behavior as demand or workload increases.

Scalability is a system’s ability to remain responsive as workload increases. Responsiveness means keeping the error rate below an acceptable error budget for a defined service-level objective. section 1.4.2 section 1.4.3

Scalability is not a property of one component alone. It emerges from multiple concurrent components and their interactions, because a single component cannot handle unbounded load. section 1.0 section 1.4.3

A practical test

A web application may work correctly with modest demand yet fail its service objective as requests increase. Adding components can support scale, but the resulting guarantee depends on how those components interact. section 1.0 section 1.4.3

How Think Distributed Systems covers it

How deep it goes
Defines responsiveness through service objectives, error rates, and error budgets, but stops short of implementation strategies.
Examples
Uses modern applications, increasing load, single-component limits, and interacting distributed components as concrete illustrations.
What it assumes
Assumes only a basic system model and develops distributed components, network communication, load, and service guarantees.
What you can do after
Evaluate scalability by defining acceptable responsiveness, service objectives, error rates, and error budgets under load.
How it connects
Connects scalability with distributed systems, correctness, reliability, responsiveness, service-level objectives, error rates, and error budgets.

Also explained in

Compare how 27 books explain scalability →

Related concepts

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