{
  "uid": "cogitave.learn.reliability-and-sre",
  "kind": "module",
  "href": "/modules/reliability-and-sre/",
  "title": "Reliability and SRE",
  "summary": "Reason about a service's reliability targets the way the reliability standard does - set an SLO from the user's journey, compute the error budget it buys, and operate the service against that budget with burn-rate alerts, sustainable on-call, a toil cap, and the freeze that stops shipping when the budget runs out.",
  "type": null,
  "products": [
    "cogitave-core"
  ],
  "roles": [
    "developer"
  ],
  "levels": [
    "intermediate"
  ],
  "subjects": [
    "it-management"
  ],
  "headings": [],
  "source": "By the end of this module, you'll be able to:\n- Explain why reliability is engineered as a budgeted feature, not chased as an absolute, and why SRE is an engineering discipline rather than a renamed ops rota.\n- Set an SLO from a critical user journey, pick the right tier target, and compute the error budget and burn rate it produces.\n- State the error-budget policy - freeze on exhaustion, one named owner, security exempt - and say what it buys operationally: sustainable on-call, a capped toil load, tested resilience, and an SLA that is always looser than the SLO behind it.\n- Read the reliability standard and ADR-0020 as the source of truth for a service's reliability posture, and know when a different value requires an Accepted RFC.\n",
  "units": [
    "cogitave.learn.reliability-and-sre.introduction",
    "cogitave.learn.reliability-and-sre.slos-and-error-budgets",
    "cogitave.learn.reliability-and-sre.operating-for-reliability",
    "cogitave.learn.reliability-and-sre.knowledge-check",
    "cogitave.learn.reliability-and-sre.summary"
  ],
  "durationInMinutes": 29,
  "badge": "cogitave.learn.reliability-and-sre.badge",
  "partOf": "cogitave.learn.paths.operate-the-estate"
}