Scaling bottleneck inventory for the current system
Every system has one resource that will run out first, and it is rarely the one the team argues about. Listing each tier, its current utilisation at peak and the resource it would exhaust (CPU, connections, disk IOPS, lock contention, a single-threaded worker) turns vague worry about scale into a short, ranked list of things to fix in order.
First tasks
- Export peak hour CPU, memory, connection and IOPS figures for each tier
- Name the resource each tier would run out of first
- Rank the three tiers closest to their ceiling
- Save the dated inventory next to the architecture diagrams