Reliability

Interfaces and recovery plans that survive ordinary failures.

Separate readiness from liveness

A running process is not necessarily ready to serve traffic. Conversely, a temporary dependency problem does not always mean restarting the process will help. Distinct health signals let the platform choose between waiting, removing traffic and restarting.

Reliability
Stop feeding a failing dependency

Repeated calls to an unhealthy dependency consume time and resources while adding pressure to the failing component. A circuit breaker temporarily rejects some calls after a defined failure pattern, then permits controlled probes to see whether service has recovered.

Reliability
Drain work before stopping

Stopping a process can interrupt requests, lose unacknowledged work or cause clients to retry a completed action. A graceful shutdown sequence gives the process a bounded opportunity to finish or return ownership of its work before it exits.

Reliability
Budget a scarce resource

A service can fail before its CPU is full. Connections, memory, queue slots or a downstream quota may become the limiting resource first. Capacity planning starts by identifying which resource bounds the workload and how demand grows with concurrency.

Reliability
Rehearse a small recovery

A recovery document is a hypothesis until someone follows it. A bounded drill checks whether people, access and procedures work together under realistic conditions. The goal is to discover missing steps before an outage makes every minute expensive.

Reliability

Search the library