ScaleCrafts

Design a view and like counter

EasyCountersBatchingEventual consistency

Count views and likes on posts and videos at huge scale and show the totals wherever they appear.

Functional requirements

  • Record a view or a like
  • Show the current count on every post
  • Users can unlike, and counts drop accordingly

Non-functional requirements

  • Counts may lag a few seconds but never drift
  • Counting never slows down page loads
  • No increments are lost

Scale

  • 1B views per day
  • Top posts get 100K views per second
  • Counts shown on 10B page loads per day

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 a view and like counter”, that starts with: Record a view or a like; Show the current count on every post; Users can unlike, and counts drop accordingly. Interviewers notice candidates who pin the requirements down first.
  • Turn the scale into numbers. The scale (1B views per day; Top posts get 100K views per second; Counts shown on 10B page loads per day) 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: Counts may lag a few seconds but never drift; Counting never slows down page loads; No increments are lost. 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 counters, batching and eventual consistency here. This is an easy problem, so interviewers expect the fundamentals done cleanly: a clear request path, the right kind of data store, and a reason for each component.
  • 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…