45 Minutes to Bring Your App to Its Knees: The Complete Guide to Load Testing
summary
This talk explains how to design and run load tests for complex distributed applications (microservices) with components like databases, APIs and SSO authentication. It covers why load testing is often done too late, what failing systems reveal (threads, JVM, DB, configuration, bottlenecks), and gives a practical guide so teams can implement load tests and improve resilience in production.
AI-written summary · about
chapters (34)
- 0:00Load testing history
- 1:13Speakers and Takiné app
- 2:38Load testing definition
- 4:24Gatling discovery
- 5:06Critical test scenarios
- 7:12Takiné architecture
- 8:14Three pillars of load testing
- 9:17Gatling boilerplate
- 10:42HTTP actions and groups
- 12:46Session variables
- 13:50Pauses for realism
- 14:10Running tests and analysis
- 15:56Integration vs load tests
- 17:18Code refactoring
- 18:49Actions and helpers
- 20:51Feeders for data
- 24:43Diverse user paths
- 25:46Realistic scenarios
- 27:11Random data
- 30:42Best practices
- 31:44Movie page scenario
- 32:27Dynamic backend data
- 34:34Load testing basics
- 35:14Authenticated contexts
- 36:17Test Gateway
- 38:44Load test data
- 40:30Industrializing tests
- 41:52Smoke tests
- 42:36Load test architecture
- 43:17Gatling Cloud demo
- 45:41Results interpretation
- 46:04When to load test
- 46:46Resources and next steps
- 47:28Conclusion
related talks
45mBeat the rush! Designing effective load tests for your web application
44mPerformance Testing: the way to make a true load
44mSofts You Need to Run the Perfect Load Test
47mQuality Control for High-Load Systems
44mLoad testing in 5 minutes. Comparison of available tools and live hacks
42mLoad testing distributed asynchronous systems
06m"Mobile App Performance Testing"
51mLoad Testing: How to Know Your Limits