Skip to content

srekit capacity

Generate a capacity plan: baseline metrics, growth assumptions, forecast, scale-up triggers, headroom targets, dependencies, cost, risks.

Synopsis

srekit capacity --service NAME [flags]

Flags

Flag Required Description
--service yes Service the plan covers
--horizon no Planning horizon (e.g. 6m, 1y, 2y). Default: 1y

Plus the shared output flags. Default filename: capacity-<slug-of-service>.md.

Examples

srekit capacity --service api-gw --horizon 6m --out capacity-api-gw.md

Longer horizon:

srekit capacity --service db-replicas --horizon 1y --stdout

Section structure

  • Front matter: title, service, horizon, id
  • Базовые метрики (Baseline metrics) — RPS, p99, CPU, memory, disk, network
  • Допущения роста (Growth assumptions)
  • Прогноз (Forecast) — table by month / quarter
  • Триггеры масштабирования (Scale-up triggers)
  • Цель по headroom (Headroom target)
  • Зависимости (Dependencies)
  • Стоимость (Cost)
  • Риски (Risks)
  • Ссылки (References)

Template shape

capacity ships as a v1 YAML artifact (internal/tmpl/templates/capacity.yaml) — frontmatter, H1, meta_bullets, sections (current_capacity, growth_assumptions, forecast, scale_up_triggers, target_headroom, dependencies, cost_implications, risks, review, references). Template expressions reference .Meta.<Field> for ID, Service, Horizon, Now. See srekit postmortem for the full schema reference.

See also

  • srekit slo — capacity constraints often follow from latency SLOs.
  • srekit rfc — file an RFC when capacity choices need broad buy-in.