Reliability & Incident Response
Incident management, chaos engineering, and runbook design.
15 topics in this category.
Incident command system (ICS)
RecommendedA standardized, hierarchical management structure designed to coordinate emergency response and eliminate chaos during severe outages.
Blameless postmortems
RecommendedThe practice of investigating outages without assigning human fault, focusing instead on the systemic vulnerabilities that allowed the failure to occur.
Mean Time To Recovery (MTTR)
RecommendedA critical metric that measures how quickly a team can diagnose, mitigate, and resolve a production outage.
Runbooks and playbooks
RecommendedExplicit, step-by-step technical manuals designed to guide engineers through mitigating specific alerts and routine operational tasks.
Chaos engineering principles
RecommendedThe discipline of experimenting on a distributed system to build confidence in its capability to withstand turbulent conditions in production.
Rate limiting strategies
RequiredTechniques for controlling the rate of traffic sent or received by a network interface controller to prevent resource exhaustion.
Circuit breaker pattern
RecommendedA software design pattern used to detect failures and encapsulate the logic of preventing a failure from constantly recurring, during maintenance, temporary external system failure or unexpected system difficulties.
Bulkhead pattern
RecommendedIsolating elements of an application into pools so that if one fails, the others will continue to function, preventing total system collapse.
Retry with exponential backoff and jitter
RequiredA network resilience strategy that spaces out repeated requests to a failing service to prevent self-inflicted Denial of Service attacks.
Uptime monitoring architecture
RequiredThe design of external, black-box monitoring systems that verify a service is actually reachable and functioning from the perspective of a user.
Incident severity classification
RequiredA standardized scale (usually SEV-1 to SEV-4) used to instantly communicate the business impact of an outage and determine the appropriate level of response.
Graceful degradation patterns
RecommendedDesigning systems to intentionally disable non-critical features during high load or partial outages to preserve core functionality.
On-call rotation design
RecommendedThe operational structures and human-centric schedules that ensure a system is supported 24/7 without burning out the engineering team.
Disaster recovery and RPO/RTO
RequiredThe strategies and metrics used to restore business operations after a catastrophic event, focusing on acceptable data loss (RPO) and downtime (RTO).
Backpressure and flow control
RecommendedThe mechanisms by which a downstream system signals an upstream sender to slow down its transmission rate, preventing catastrophic resource exhaustion.