Five Design Patterns to build resilient Applications
summary
Shows a demo app (React front end, .NET proxy) calling a flaky third‑party joke API and applies five concrete patterns using Polly and AWS Fault Injection Simulator to prove them. Implements timeout 5s on HttpClient, a fallback that returns one canned joke, a retry loop of 5 retries with exponential backoff plus jitter (0–1000ms), and a circuit breaker that opens after 5 failures for 1 minute. Chaos experiments stop EC2 instances to validate the improvements.
AI-written summary · about
chapters (23)
- 0:00Start
- 1:15Background
- 2:58Failure Is Bad
- 4:21Chaos Engineering
- 6:10React App
- 15:49Graceful Degradation
- 16:15Fallback
- 18:18Policy Wrap
- 20:46Retries
- 21:30Retry Policy
- 23:54Retry Pattern
- 26:26The Exponential Back Off
- 29:32Clustering
- 31:33Pattern Five
- 32:37Circuit Breaker
- 41:24Phase of Chaos Engineering
- 44:23Observability
- 45:56Fault Injection Simulator
- 47:11Social Engineering
- 55:22Social Engineering Attack
- 1:01:15Five-Step Plan
- 1:02:38Sim Swap
- 1:14:16Face Plate
related talks
52mPerformance & Stability Anti patterns
47m8 Cloud Design Patterns you ought to know.
57mResilient Cloud Architecture Design Patterns
25mDesigning and Testing Resilient APIs for India Scale
56mSystem Stable : Robust connected applications with Polly
49mPatterns for resilient, highly available cloud architectures
42mBulletproof Transient Error Handling with Polly
01h 02mBuilding cloud-ready applications in .NET