Site Reliability Engineering interview question · Most asked
How do you do capacity planning for a service?
Summary
Forecast demand (organic growth, launches, seasonal peaks), measure how much load each instance or resource can handle through load testing, and provision for peak plus a safety margin and the loss of a failure domain (N+1 or N+2, zone loss). Revisit regularly and automate scaling where possible.
Longer Answer
Steps: know the service's bottleneck resource and its saturation point (load tests, production measurements); model demand per business driver (requests per active user); plan for redundancy (survive losing a zone at peak); include lead times for things that cannot autoscale (database instances, quotas, reserved capacity, hardware). Watch cost: overprovisioning is also a failure. Track forecast accuracy and adjust.
Key Points
- Forecast demand including peaks and launches.
- Measure per-unit capacity with load tests.
- Plan N+1 / zone loss.
- Account for lead times and quotas.
More most-asked Site Reliability Engineering questions
- What is Site Reliability Engineering, and how does it relate to DevOps?
- What makes a good alert? Explain symptom-based alerting and alert fatigue.
- What is an error budget, and how should it be used?
- Define SLI, SLO and SLA, and explain how they relate.
- What is burn-rate alerting, and why is it better than alerting on raw error rates?
- How do you choose good SLIs for a service?
- What are the four golden signals?
- What is the difference between monitoring and observability? Explain metrics, logs and traces.