advancedSystem Design121 of 132
A service receives 100K requests per second. How would you scale it?
Tests whether you identify the actual bottleneck first (stateless app tier horizontal scaling is usually easy; the database and any shared stateful component are the hard part) rather than jumping straight to 'add more servers' without naming what needs caching, sharding, or read-replica offloading.
Ready to design this system end to end?
Generate a complete, structured system design answer — requirements, capacity estimation, API design, architecture, database choice, scaling, caching, fault tolerance, security, trade-offs, and more, walked through the way a strong senior engineer would in a real interview.
Sign in to generate a responseNext Step
←PreviousContinue to Notification service with email, SMS and push. The SMS provider dies for 20 minutes. What happens to email and push?→
← Back to all System Design (HLD) questions