[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"lesson-software-architecture-availability-and-resilience-resilience-patterns-en":3,"cheat-sheet---en":3,"domain-info---en":3,"prev-software-architecture-availability-and-resilience-resilience-patterns-en":3,"next-software-architecture-availability-and-resilience-resilience-patterns-en":3,"topic-info-software-architecture-availability-and-resilience-resilience-patterns-en":4,"course-lesson-metadata-software-architecture-en":19},null,{"meta":5,"body":8},{"title":6,"description":7},"Resilience Patterns","Timeouts, retries, circuit breakers, bulkheads, and graceful degradation for calls that fail.",{"type":9,"value":10,"toc":15},"minimark",[11],[12,13,14],"p",{},"In a distributed system, a slow dependency is more dangerous than a dead one. This topic studies how failures cascade, then arms every call path: timeouts that bound the damage, retries with backoff and jitter, circuit breakers that stop hammering the wounded, bulkheads that contain the blast, and degradation modes that keep the core alive.",{"title":16,"searchDepth":17,"depth":17,"links":18},"",3,[],{"lessons":20,"cheatSheets":21,"mockTestsAvailable":22},[],[],false]