Enabling Product Scalability through Load Testing
summary
Load testing validates migration of legacy group chats into Forums to support 10x group size, using scripts to create rooms and add users, Grafana dashboards for SLIs, and distributed tracing to pinpoint slow hops. Early backend-only tests succeed after batching and chunking fixes but real users trigger extra UI-driven traffic, so a VM fleet runs concurrent UI clients for full end-to-end tests. Final result: completed migration to Forums with updated tests and monitoring that catch latent failures. end-to-end UI simulation
AI-written summary · about
chapters (9)
- 0:00Load testing introduction
- 1:18Product and migration goals
- 3:50Planning load tests
- 7:44Stakeholder review and isolation
- 9:07Backend load tests
- 11:17Bottlenecks with tracing
- 13:24System improvements
- 14:46UI and user tests
- 16:11Lessons learned
related talks
33mPros/Cons of Highly Scalable Microservice Systems
45mMonitor, Fix and Deploy (on Friday)
21mTesting in Production at Scale
53mHow do we build high‑load microservices
42mLoad testing distributed asynchronous systems
40mDeploying node.js at scale
22mLessons Learned from Scaling RabbitMQ in a High-Growth (...)
40mDecomposing a live application with confidence