Building Resilient DevOps Pipelines: Strategies for Handling Unexpected Failures &...
summary
Promises concrete failure-handling patterns: redundant instances, automatic failover, replica databases, and capacity planning tied to RPO and RTO targets. Describes monitoring/observability at application, node, container and Kubernetes levels and gives traffic examples like e‑commerce Thanksgiving spikes. Names chaos tools and frameworks — Chaos Monkey, Litmus, Gremlin — and cites case studies from Uber, Netflix and Meta showing how microservices, regional isolation and distributed replication actually behave. Useful if wanting specific tools, metrics and worked examples rather than high‑level platitudes.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:13Agenda and fault tolerance
- 4:06Stress in deployments
- 8:44Fault tolerance principles
- 13:21Resilient pipeline strategies
- 17:21Case studies: Uber and Meta
- 19:07Disaster recovery planning
- 20:32Chaos engineering practices
- 22:18Key takeaways
- 23:42Q&A
related talks
51mDesigning for Failure: Build Resilient Services
45mDeveloping a Chaos Architecture Mindset
26mBreaking Systems for Resilience
16mEngineering Failure-Resilient Systems
01h 02mPractical Chaos Engineering breaking things on purpose to make them more resilient against failure
48mChaos Engineering: The Path to Reliability
18mChaos Engineering: Break It On Purpose
44mBuilding Resilient Application Deployments on Kubernetes