ScaleCrafts

Design a website uptime monitor

EasySchedulingWorkersAlerts

Check websites every minute from several regions and alert owners the moment one goes down, like UptimeRobot.

Functional requirements

  • Register a URL to check every 1 to 5 minutes
  • Alert by email or SMS when a site goes down or recovers
  • Show uptime history and response times

Non-functional requirements

  • Alerts within 2 minutes of an outage
  • No false alarms from one bad network path
  • Checks keep running if one region fails

Scale

  • 1M monitored URLs
  • About 15K checks per second
  • 90 days of history

How you’ll be scored

10 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 website uptime monitor”, that starts with: Register a URL to check every 1 to 5 minutes; Alert by email or SMS when a site goes down or recovers; Show uptime history and response times. Interviewers notice candidates who pin the requirements down first.
  • Turn the scale into numbers. The scale (1M monitored URLs; About 15K checks per second; 90 days of history) 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: Alerts within 2 minutes of an outage; No false alarms from one bad network path; Checks keep running if one region fails. 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 scheduling, workers and alerts 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…