Capacity Estimation of the Webpage System Design
Here are some capacity assumptions we can make for this system:
2.1. Traffic Estimates
Active Users = 10 million
Daily Active Users (DAU) = 5 million
Profile requests per user per day = 10
Total requests per day = 50 millionAvg QPS = 50 million / (24 hrs x 3600 sec/hr) = ~580 requests/sec
Peak QPS = 2 x 580 requests/sec = 1160 requests/sec
2.2. Storage Estimates
200 bytes for name = 200MB
500 bytes for photo = 500MB
10 bytes for badge ID = 10MB
4 bytes for points = 4MB
Total storage per user = 714 bytesFor 10 million users: Storage needed = 7.14 TB
2.3. Bandwidth Estimates
Profile data fetched per request
200 bytes (name)
500 bytes (photo)
10 bytes (badge)
4 bytes (points)
Total = 714 bytes
Daily active users = 5 million
Profile requests per user per day =10
Requests per day = 50 millionDaily Bandwidth: 50 million x 714 bytes = ~35 GB/day
Design a webpage that can show the status of 10M+ users including: name, photo, badge and points | System Design
We’ve got this huge community—over 10 million strong—and you want to build a webpage where everyone’s details, like their names, photos, those cool badges they’ve earned, and their points, can all be seen. That’s a massive load of information to handle. Achieving this goal necessitates an efficient and scalable system architecture capable of handling immense data volumes without compromising on performance or user experience.
Important Topics for the Webpage System Design
- Requirements of the Webpage System Design
- Capacity Estimation of the Webpage System Design
- High Level Design of the Webpage System Design
- Database Design of the Webpage System Design
- How to show the status of 10 million users
- Communicating with the servers in Webpage System Design
- Database Architecture of the Webpage System Design
- Low Level Design of the Webpage System Design
- Work Flow of Webpage System Design
- How to make the system Scalable?