TechPrep
The design methodReadLabPracticeCheck

Requirements and estimation

Turn a vague prompt into numbers that decide the design: peak load, storage growth and fan-out, each with its uncertainty.

Estimation is not a ritual. Do it only to answer a question the design depends on: one database or many? Does it fit in memory? Can one region serve it? Stop as soon as the answer is clear.

Numbers worth knowing

QuantityRule of thumb
Seconds in a day~86,400; use 10⁵ and say it is 16% high
Peak to average2 to 10x depending on how diurnal the traffic is; consumer apps often ~3x
Memory read / SSD read / same-region round trip / cross-continent round trip~100 ns / ~100 µs / ~0.5 ms / ~100 ms+
One modern serverTens of thousands of simple requests per second; a single relational primary handles thousands to tens of thousands of writes per second depending on row size and indexes
LLM output speedTens to low hundreds of tokens per second per stream; varies by model and provider, so ask or state the assumption

These are order-of-magnitude anchors, not benchmarks. Say "I'll assume" and move on; the interviewer cares that the assumption is explicit and that you know which way it would move the design.

Requirements that change architectures

Capacity estimator

Change any input. Outputs are simple products; the point is to see which input dominates.

Average requests/s-
Peak requests/s-
Peak writes/s-
New data per day (GB)-
Stored over retention, replicated (TB)-
Servers at peak (no headroom)-

Decimal units (1 GB = 10⁹ bytes). Add headroom for failover: N + 1 per zone at minimum.

Practice

Written for this site to drill the lesson. Not reported interview questions.

  1. A chat app has 50M DAU sending 40 messages a day of 300 bytes. Estimate peak writes per second and a year of storage at RF 3.
  2. An internal RAG assistant serves 20,000 employees asking 15 questions a day. Estimate peak queries per second and the daily token volume at an assumed 3,000 input and 400 output tokens per query.
  3. For one of the two above, name the single input whose uncertainty matters most and why.

Check yourself

When should you stop estimating?

As soon as the numbers answer the design question you were estimating for.

Name three requirements that can change the architecture on their own.

Any of: read/write ratio, consistency need, latency percentile target, durability (RPO/RTO), tenancy or data residency.

Saved in this browser.