Multi-domain scenarios and its business impacts
summary
Explains a practical playbook: identify repeatable failure modes, reuse AWS experiments across services and convert them into an agile experiment bucket that runs manually then automate experiments into CI/CD for daily health checks. Recommends starting with open‑source chaos tools, sequencing hits from infra → network → API, and mapping outcomes to money — e.g. a discovered 30% transaction rejection during HA failover converted into lost‑revenue and man‑hour estimates to justify remediation.
AI-written summary · about
chapters (8)
- 0:00intro
- 0:22preamble
- 1:14agenda
- 1:32creating impact on multiple domains
- 6:54creating value to business
- 11:3711:36 creating value with technology
- 16:01Q&A
- 16:27thank you for your patience
related talks
47mImproving Business Resiliency with Chaos Engineering
50mDevOps Project Failures - Lessons Learned and Strategies for Recovery
28mHalloween Horror Stories from the Trenches
40mThe Resilience Business Case: Three Case Studies
42mHow to foster a Culture of Resilience
18mScaling DevOps in Complex Environments: Challenges, Failures, and Successes
46mContinuous Experimentation
01h 06mCongratulations, you Failed!