Traffic spikes exceed the capacity of a critical resource.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Theoretical construct: explains a term, principle, or mental model.
Concrete cog in the system that works inside larger relationships.
A capacity bottleneck occurs when a limited resource determines a system's performance under growing or fluctuating demand.
Capacity planning became a standing availability responsibility in Site Reliability Engineering: Google describes capacity as critical to availability and therefore assigns planning and provisioning to the SRE team.
The slowest or most heavily loaded part sets the throughput ceiling. When demand exceeds it, queues and latency grow; more capacity, load shedding, or more efficient processing moves that boundary.
Requests and workload fluctuate over time.
A resource constrains throughput or response time.
Capacity is forecast from expected load and safety reserves.
Finding the bottleneck directs scaling and load tests toward the resource that actually limits user impact.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.