The ugly side of scaling a SAAS application from 0 to 2B+ requests/month
summary
Concrete account of the technical challenges eNotas faced while scaling a SaaS product from initial versions to handling over 2 billion requests per month. Covers the specific scaling problems encountered and the solutions and techniques used to overcome them (architecture, performance and operational fixes implied by the description).
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:51Speaker background
- 3:37Why the ugly side of scale
- 6:07MVP and legacy systems
- 12:14Legacy system challenges
- 17:15Observe development
- 25:27First bottleneck overcome
- 26:10Design for failure
- 29:27Eventual consistency
- 38:34High-load scaling problems
- 47:49Resilience and recovery
- 53:09Summary and next steps
- 53:57Q&A
related talks
56mMastering Cloud Scalability and System Designs Deep dive
45mScaling under uncertainty
46mDigital scale-up architectural patterns
34mWhen scalability becomes more than a buzzword, or how to saddle an unicorn
41mFrom Zero to 10 million: Architecting for scale on AWS
33mWhen scalability becomes more than a buzzword, or how to saddle a unicorn
48mCrashmanship, Architecture from Start-up to Scale-up
32mScaling Done Right