Load Testing AWS Serverless Architectures with Serverless
summary
Claims that load testing must verify actual scaling behaviour and costs not just architecture diagrams, and demonstrates using Serverless Artillery (Artillery on Lambda) to drive massive parallel traffic, measuring cold starts, throttles and cost-per-action. Shows a live case (Gamercraft) and advises observability with CloudWatch X-Ray and a dedicated provider, replicating prod per test, committing repeatable scenarios, and to run load tests from a different AWS account. Notes real limits like Cognito list-users 30/s hard limit and Lambda default 1000 concurrency.
AI-written summary · about
chapters (6)
- 0:00Intro
- 0:46What is Serverless
- 6:03What is Load Testing
- 10:40Where to Start
- 12:02Metrics
- 14:10Load Testing Toolkit
related talks
47mAdvanced Serverless Architectural Patterns on AWS
44mServerless Architecture on Production: Good, Bad and Ugly Parts
50mServerless Architecture Patterns and Best Practices
51mArchitecting for Hyperscale with AWS: Navigating Real-world Serverless Challenges
30mPerformance Tales of Serverless
01h 00mServerless - reality or BS - notes from the trenches
49mServerless Architectural Patterns and Best Practices
44mApplying principles of chaos engineering to serverless
