ScaleCrafts

Design an ad click aggregator

HardStreamingAggregationExactly-once

Count billions of ad clicks in near real time so advertisers see results and are billed accurately.

Functional requirements

  • Record every ad click and redirect the user
  • Advertisers query clicks per ad per minute
  • Billing uses final, accurate counts

Non-functional requirements

  • Clicks are counted exactly once
  • Dashboards lag by under a minute
  • Redirects stay fast

Scale

  • 10B clicks per day
  • Peaks of 1M clicks per second
  • Data kept for 2 years

How you’ll be scored

9 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works

What interviewers look for

  • Clarify before you draw. State what is in and out of scope. For “Design an ad click aggregator”, that starts with: Record every ad click and redirect the user; Advertisers query clicks per ad per minute; Billing uses final, accurate counts. Interviewers notice candidates who pin the requirements down first.
  • Turn the scale into numbers. The scale (10B clicks per day; Peaks of 1M clicks per second; Data kept for 2 years) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
  • Show how each quality is met. Your design should visibly deliver: Clicks are counted exactly once; Dashboards lag by under a minute; Redirects stay fast. Saying that it does isn’t enough; point to the part of the design that makes it true.
  • Expect follow-ups on the hard parts. Interviewers usually probe streaming, aggregation and exactly-once here. This is a hard problem, so interviewers expect depth: what breaks first at this scale, how each failure is contained, and which trade-offs you accepted on purpose.
  • Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.

Related problems

Loading your workspace…