Scaling Done Right
summary
Practical guidance for building services that scale to millions, using Amazon Alexa lessons: choose between replicate monoliths, microservices, or serverless with clear trade-offs; plan for extreme spikes (think 50x, not 5–10x); set concrete SLAs/latencies per user action; test backups by deleting all data and doing a full restore from backup before launch; measure recovery time, autoscaling limits, retry policies, monitoring and logging; simulate failures — break the system regularly — and document/manual steps so customers always see a clear support/communication path.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:17Why the Question of Scaling Is Important
- 8:55How To Make a Right Decision about the Scaling
- 9:30Working Backwards
- 10:54Customer Experience
- 18:25Cons
- 20:32Customer Obsession
- 23:03Backups
- 26:21Planning Capacity
- 28:56Communication
related talks
41mFrom Zero to 10 million: Architecting for scale on AWS
56mMastering Cloud Scalability and System Designs Deep dive
31mMastering the Balancing Act: Scaling Infrastructure for Growth and Stability
19mEngineering for the Long Game
40mThe Art of Embracing Failure at Scale
45mScaling under uncertainty
15mDevOps at scale
40mScaling Startup for Success: Building modern Architectures and Developer Acceleration