
< session />
Wed, April 28Reliability, Observability & SecurityArchitecture & Distributed Systems
Small things going wrong can quickly snowball. A problem that seems minor in isolation can trigger a chain reaction of increasing failures, potentially leading to catastrophic results. When the failure of a single component causes other connected elements to fail, this is known as progressive collapse.
In this session, you will examine how progressive collapse occurs and how it has manifested in major disasters. Drawing on lessons from other industries, you will explore three techniques for mitigating progressive collapse and learn how to architect systems so that small failures stay small.
What You Will Learn
How small failures can develop into cascading failures and progressive collapse
What major disasters can teach us about progressive collapse
Three techniques for mitigating progressive collapse and keeping small failures contained
Who Should Attend
Software Architects, Developers, Technical Leads, and practitioners responsible for designing resilient systems.
< speaker_info />
Sam Newman is an independent consultant who loves solving problems with technology. Focusing primarily in the areas of cloud, microservice architecture and continuous delivery, Sam works with companies big and small all over the world. He is also an experienced conference speaker, and author of the O’Reilly books Monolith To Microservices, Building Microservices, and the forthcoming Building Resilient Distributed Systems.