Managing Resiliency in Microservices
summary
Builds a simple frontend/backend weather service, adds Redis caching and demonstrates retries with exponential backoff and jitter, plus a circuit breaker that opens after repeated failures (opens for ~15s). Uses Tye to run and deploy locally, applies code policies with Polly (wait-and-retry, circuit breaker), then shifts to infra-based resiliency with Linkerd service mesh where retries are configured in YAML. Demos show errors hidden by retries and the infra approach working across heterogeneous services.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:43Microservices: for faster app development
- 4:14Is Monolithic bad?
- 5:12Microservices Architecture
- 8:56Building resilient cloud applications
related talks
40mLet it fail: resilience patterns for microservices
30mMaking Your Apps and Infrastructure Services Failure-Resilient with...
01h 00mSystem Stable: Robust connected applications with Polly, the .NET Resilience Framework
50mSurviving Scale: Patterns for Evolving Failure-Resilient Microservices
14mImplementing Resilience with Micronaut
25mResilience testing in modernization projects
32mBeyond Optimization: Resilient Cloud Microservices at Scale
38mDurable Execution: The Next Leap for Microservices Architectures