How We Protect Millions of Customers During Overloads
summary
Describes protecting millions of users from cascading failures caused by overloads in high-load systems by isolating and limiting cross-component impacts. Explains concrete engineering techniques and architectures used to prevent one overloaded component from making other services unavailable, based on real production experience.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 6:24Service overload problems
- 10:40Finding protection solutions
- 13:26Static limits implementation
- 17:57Static approach drawbacks
- 18:40Dynamic throttling implementation
- 33:48Approach comparison example
- 36:59Conclusions and recommendations
- 39:04Q&A
related talks
25mAvoiding Overload in Distributed Systems
59mHow to Survive Under Load: Fault-Tolerant Server, Smart Client
47mTop infrastructure mistakes that hinder high loads
10mDesigning for Failure using AWS: Resilient Systems
34mDistributed Systems - What Can Go Wrong and How to Get It Right
29mBuilding Resilient Systems
10mBuilding an 'Oops-Less Operation' at Scale
34mBuilding High Resiliency into Digital Solutions