Making Your Apps and Infrastructure Services Failure-Resilient with...
summary
Configuration-driven resilience using Dapr 1.7 resiliency policies applies timeouts, retries (constant or exponential) and circuit breakers to apps, components and actors via YAML/CRDs. Targets include state stores, pub/sub and bindings; demo overloads Cosmos DB (Azure Service Bus + Cosmos DB) producing 429s, then a circuit breaker (trip: consecutive failures >1, timeout 60s, interval 30s, maxRequests 1) stops retries and prevents further overload. Circuit breakers live per sidecar, policies merge across CRDs so many apps share the same behavior.
AI-written summary · about
chapters (4)
related talks
49mStart Building Distributed Applications with Ease Using Building Block APIs
49mManaging Resiliency in Microservices
37mStart building distributed applications with ease using building block APIs
51mDesigning for Failure: Build Resilient Services- 49mStart Building Distributed Applications with Ease Using Building Block APIs
01h 03mDeveloping microservices like a boss with Dapr and Azure Container Apps
58mResilient by Design
44mArchitectural Patterns of Resilient Distributed Systems