liveBook · Manning

Scalability

As explained in Fast by Default

Scalability is the ability of a software system to maintain acceptable behavior as demand, workload, or system size increases.

Scalability is the ability of a software system to maintain acceptable behavior as concurrency, workload, data volume, and system complexity increase. It differs from speed, which concerns one user’s critical-path latency, and resilience, which concerns behavior during failures or degradation. section 4.5 section 5.1

Scaling exposes successive bottlenecks rather than one universal performance problem:

  • Database queries that take milliseconds at small scale can take seconds as data and traffic grow. section 4.5
  • Connection pools that support development traffic can become exhausted in production. section 4.5
  • Caches that fit comfortably in memory can exceed their bounds as the working set expands. section 4.5
  • Resource contention, query patterns, connection pooling, and horizontal scaling determine how latency changes under load. section 5.1

Sequential service calls

A page that waits for seven sequential backend calls—such as pricing, inventory, promotions, and customer preferences—can remain slow despite optimized JavaScript. Architectural choices set the performance ceiling, so the dependency path must be addressed rather than optimized only at the client. section 5.0

Design for expected growth without over-engineering hypothetical scale. Establish load-dependent performance baselines, compare p50 and p99 latency across increasing traffic, and select patterns that degrade gracefully as demand rises. Treat scalability as an architectural constraint alongside functionality and maintainability. section 4.5 section 5.1

How Fast by Default covers it

How deep it goes
Explains bottleneck progression, measurement, and architectural dependencies but stops short of detailed implementation patterns.
Examples
Uses database growth, exhausted connection pools, overflowing caches, and seven sequential backend calls as concrete failure patterns.
What it assumes
Distinguishes speed from scalability and resilience while assuming familiarity with APIs, databases, caches, and production traffic.
What you can do after
Evaluate scalability by comparing p50 and p99 latency under increasing load and identifying the responsible architectural bottleneck.
How it connects
Connects scalability with speed, resilience, resource contention, connection pooling, databases, caching, and horizontal scaling.

Also explained in

Compare how 37 books explain scalability →

Related concepts

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