sre

It aggregates the essential SRE knowledge base: on-call practices, incident response procedures, SLI/SLO/SLA frameworks, error budget management, postmortem templates, capacity planning approaches, and the tooling ecosystem around observability, alerting, and automated remediation.

Content is organized around the SRE lifecycle: designing reliable systems from the start (architecture patterns for high availability, graceful degradation, circuit breakers), operating them in production (monitoring, alerting, runbooks, escalation paths), responding to incidents (communication templates, severity classification, war room coordination), and learning from failures (blameless postmortem culture, systemic improvement tracking).

References to Google's published SRE books, the DORA research program, and industry incident reports provide authoritative grounding for the practices documented.

Software engineers transitioning into SRE or platform engineering roles use this collection to build structured knowledge of reliability practices beyond their development background. SRE teams formalizing their runbooks and incident response procedures use it as a reference for industry norms and templates.

Engineering managers building reliability programs at growing companies use it to understand the practices and tooling their teams should adopt as they scale from startup infrastructure to systems where downtime has meaningful business consequences.