Scale out or fix the bottleneck? How on-call engineers decide during capacity incidents
When latency spikes during an incident, engineers often face pressure to simply add servers or increase instance sizes. The article argues that scaling is the fastest mitigation, useful as a buffer when traffic growth is real and the application is stateless. However, scaling can backfire when all instances share a constrained database, since connection counts and lock contention may cap gains while costs rise. Scaling can also replicate misconfigurations across a fleet and yields diminishing latency improvements for inefficient workloads. The piece recommends treating persistent slowdowns as signals to profile queries, traces, and resource usage, while acknowledging that proper root-cause fixes may take longer than an active incident allows.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in