Application reliability with Azure Load Testing and Chaos Studio Q&A
summary
Demo app uses AKS, Cosmos DB, Key Vault and Redis while combining Azure Load Testing to generate user traffic and Chaos Studio to inject faults; common experiments include AAD outage, DNS failure, availability zone down and Redis cache shutdown. Tests tie into CI/CD via GitHub Actions or Azure DevOps so SLO-based load checks run in minutes while multi-parameter capacity sweeps take hours. Onboarding is resource-level with RBAC controls, experiments validate monitoring and can trigger redeploy/self‑heal workflows; full repro repo and virtual lab are provided.
AI-written summary · about
chapters (18)
- 0:00Welcome
- 1:58Load testing overview
- 7:29Load testing examples
- 9:17Safety in Chaos Studio
- 11:51Top chaos faults
- 13:21Caching failures scenarios
- 16:39Chaos improves monitoring
- 18:49Q&A
- 23:06Time investment
- 27:03Chaos Studio best practices
- 31:40Compliance reports
- 33:08Load + chaos experiments
- 34:52Network security failures
- 35:57GPU load testing
- 37:02Client secret expiry
- 37:47Infrastructure resiliency
- 39:59Load + fuzzing
- 41:30Closing
related talks
25mImprove Application Resilience using Azure Chaos Studio
34mStress-Test tools in Azure to optimize your reliability
34mResilient Cloud App: Chaos Engineering, Azure Studio
32mImplementing Chaos Engineering in Kubernetes
40mWho tests their cloud code anyway?
55mPerformance Testing From Zero to Hero with K6 & Azure
29mAzure Load Testing in action
33mChaos Engr at Microsoft with Azure Chaos Studio