resilience-testing

Create a failure mode catalog by analyzing RFC documents and dependency maps to enumerate potential failure scenarios for all external dependencies. This identifies how each dependency might fail and documents the expected system behavior for each scenario.

Blast radius analysis maps the cascading effects of failures across your deployment topology to determine impact scope. It identifies which services are affected when a dependency fails and recommends isolation strategies to contain the damage.

Test circuit breaker transitions by designing a latency injection plan that simulates network delays and timeouts on dependencies. This verifies that circuit breakers open, trip, and recover correctly to prevent cascading failures.

Yes, generating a resilience test plan requires RFC or architecture documents, deployment topology, and dependency maps as input. These provide the structural context needed to identify failure modes and map cascading effects accurately.

Verify graceful degradation by designing latency injection tests that simulate slow or unresponsive dependencies. This validates that your service remains stable and provides fallback behavior instead of crashing when dependencies experience issues.

Avoid automated resilience testing when you lack complete deployment topology and dependency maps, or when testing failure scenarios in production could cause unacceptable disruption to live traffic without proper isolation boundaries.