Course contentsShow
← System Design
Lesson 1497 of 1,91937. Real-World System: URL ShortenerFree lesson

Estimating Daily Active Users and Traffic

Calculate expected daily URL creations and redirects based on user base assumptions.

Estimating Daily Active Users and Traffic

What you'll learn: How to translate user base assumptions into concrete daily traffic numbers for a URL shortener system.

Why Traffic Estimation Matters

Before you architect a URL shortener, you need to quantify the problem. How many short URLs will users create per day? How many redirect requests will your system handle? These numbers drive every downstream decision—database choice, server count, bandwidth provisioning.

The Estimation Process

Start with a user base assumption. Let's say your URL shortener has 100 million monthly active users (MAU).

Daily Active Users (DAU)

Not all monthly users come daily. A typical DAU/MAU ratio for web services is 20-30%. Using 20%:

DAU = 100M × 0.20 = 20 million users per day

URL Creation Rate

Most users consume (click) shortened URLs but don't create them. Assume only 1% of DAU create URLs, averaging 2 URLs per creator:

Daily creations = 20M × 0.01 × 2 = 400,000 URLs/day

URL Redirect Rate

The read-heavy nature of URL shorteners means clicks far outnumber creations. Use a 100:1 read-to-write ratio:

Daily redirects = 400,000 × 100 = 40 million redirects/day

Peak Traffic Multiplier

Daily averages hide reality. Apply a 3x peak multiplier for capacity planning:

Peak URL creations = 400K ÷ 86,400 × 3 ≈ 14 per second
Peak redirects = 40M ÷ 86,400 × 3 ≈ 1,400 per second

Key Takeaway: Traffic estimation transforms vague scale requirements into concrete numbers (URLs/second, requests/day) that inform database sizing, caching strategy, and server provisioning—always account for peak loads, not just averages.