[ Keynote preview ] Resiliency in Distributed Systems: Beyond Just Two Copies Behind a Load Balancer
summary
Keynote preview argues that resilient distributed systems require more than two identical service instances behind a load balancer; it grounds that claim in resilience engineering and safety management principles, treats APIs as arrows that create and limit failure modes, names concrete practices like on‑call rotations, runbooks and chaos testing as tools, and centers human factors—team structure, decision processes and monitoring—over vague promises of redundancy.
AI-written summary · about
related talks
01h 05mKeynote - Without Resilience, Nothing Else Matters
44mArchitectural Patterns of Resilient Distributed Systems
51mDesigning for Failure: Build Resilient Services
30mDistributed system design
58mResilient by Design
50mSurviving Scale: Patterns for Evolving Failure-Resilient Microservices
44mHighly Available, Distributed & Resilient Software... Team
51mHighly Available, Distributed & Resilient Software... Team