Embracing Resilience in CD Pipelines
summary
Argues that adding a disciplined Kos step into Harness CD pipelines finds faults early, using Litmus Kos and Harness CD APIs; cites downtime cost ~$5.6k per minute and 39% customer loss to motivate it. Demo runs a CPU hog experiment against an online-boutique microservices app, evaluates probes (card service availability, page latency, port checks) and computes an expected resilience score 90 so failures (66) trigger an automated rollback while successes (100) proceed.
AI-written summary · about
chapters (9)
- 0:00intro
- 0:22preamble
- 0:50agenda
- 1:39chaos in cd pipelines?
- 2:23some interesting stats
- 3:03how to improve these stats?
- 3:20why chaos step in cd pipeline?
- 9:00just a meme
- 21:16thanks!
related talks
29mEngineering Chaos for Resilient Applications: A Gameday Guide
01h 01mMastering Resilience Probes: Simplify chaos hypot...
28mBuilding Resilient DevOps Pipelines: Strategies for Handling Unexpected Failures &...
26mA proactive approach to resilience in modern apps
40mResilience Testing - Failure is an Option
42mHow to foster a Culture of Resilience
37mReactive to Proactive Continuous Resilience
45mSelf-Healing Pipelines? Resilient Deployments with Hardened Containers
