> "Now instead of one request, dozens are sent. Because the application is so much more usable this way, the number of users increases. Thus capacity demands increase by multiple orders of magnitude, which requires quantum leaps in support infrastructure." **Source**: Thomas A. Limoncelli, Strata R. Chalup, Christina J. Hogan - *The Practice of Cloud System Administration* ## Context Modern applications (especially with AJAX, mobile, real-time features) generate far more requests than traditional page-based web apps. Success compounds: better UX attracts more users, who generate more load. ## Multiplication Factors | Evolution | Request Multiplier | |-----------|-------------------| | Page-based → AJAX | 10-50× | | Desktop → Mobile | 2-3× (more sessions) | | Static → Real-time | 100×+ (WebSockets, polling) | | Success | User growth compounds everything | ## Planning Implications - **Don't plan linearly**: Growth is often exponential - **Build for headroom**: Current capacity is already insufficient - **Automate scaling**: Manual capacity planning can't keep pace - **Design for graceful degradation**: System should survive overload ## Warning Signs - Linear infrastructure planning for exponential growth - "We'll scale when we need to" without foundation - Success metrics without capacity correlation ## Related Concepts - [[Scalability Estimation]] - [[Horizontal Scaling Foundation]] - [[Future Growth Options]] ## Tags #system-design #capacity-planning #growth #operations