Challenge 1: Scale a web app to 10,000 RPS
The situation
You inherit one web server and its relational database. The site has grown: at this traffic the one server drops most requests, and the ones it answers are slow.
Traffic
10,000 requests a second.
| Operation | Share | Steps |
|---|---|---|
| Read | 90% | Read data |
| Write | 10% | Write data |
- Read90%Read data
- Write10%Write data
Data
A cache answers 85% of the reads that reach it.
What you are proving
Scalability, not performance: the same system has to carry far more traffic without slower responses, and without one machine whose failure stops it.
Rules
- The relational database stays, and every write is stored in it.The application's data is already there.
- A CDN cannot answer these requests.Every page is personalized, so no two users get the same response.
Builds on
Targets
- Serve all 10,000 requests a second
- At least 99.9% available, with no single point of failure
- At most 2,250 USD a month
- Every write kept in a relational database
- No tier over 80% busy