Capacity Estimation

Estimate the scale of the system. Consider daily active users, read/write ratio, storage requirements, bandwidth, and any relevant QPS calculations...

Estimations:

Total Users: 10M

Daily Active Users: 500K (5% of total users)

Resources created daily -> 1 URL per day -> 500k writes/day

Read/write Ratio: 1:100 -> 50M reads/day

Register Sice: ~500B (key, original url, timestamp, overhead)

Trafic:

Writes: 500k / 86,400 = 6 QPS (queries per second)

Reads: 50M / 86,400 = 580 QPS avarage (queries per second) with spike ~3x = 1.7k QPS

High read required, low latency, high availability

Trafic Increase:

2x yearly in Daily Active Users

Year	DAU	Writes/día	Reads/día
1	500k	500k	50M
3	2M	2M	200M
5	8M	8M	800M (~9.3k QPS)

Storage:

With the trafic Increase in year 5 we will require around 2.8 TB of storage

In this case we will be expecting to have database sharding, because this table can be increasing all the time, we will never delete any data in the database

Submissions

Displaying Solutions with Scores Ranging from 1 to 10

Submissions

Displaying Solutions with Scores Ranging from 1 to 10