Best practices for continuous testing and observability
summary
Shows concrete tooling and outcomes: uses AWS Fault Injection Simulator to terminate 50% of instances in an Auto Scaling group and CloudWatch Synthetics canary that runs every minute, and the ASG replaces the terminated node immediately. Demonstrates load testing (ApacheBench, 10 users ~10k–100k requests) that produces 13% failures and high latency, and Amazon DevOps Guru pinpoints DynamoDB throttling and 6–7x CPU/DB load with offending SQL, plus recommendations and integration points (CodeGuru, Device Farm, CloudWatch, EventBridge).
AI-written summary · about
chapters (13)
- 0:00Start
- 1:31Software development -testing
- 2:48Types of software testing Functional testing
- 4:59Continuous testing: DevOps
- 7:46Applying chaos engineering to your workflow Improve Steady
- 8:53Chaos engineering: How to get started?
- 10:49AWS Fault Injection Simulator
- 12:35Components
- 13:06Experiment templates
- 15:12Automated experiments
- 27:46Continuous testing: Shift left IT Ops
- 31:01Serverless: Amazon DevOps Guru
- 41:06Resources
related talks
20mResilient and well-architected apps with chaos
13mAWS for Testing – Top 3 Use Cases
39m"TestOps: Chasing the White Whale"
01h 08mPerformance testing in the cloud
26mImprove application resilience with chaos engineering
40mSh... Fail Happens: Fail-aware Events Processing on AWS
22mLooking Back to Look Forward
46mOperating EDA with Quality in Mind