ScaleCrafts

Design a stock exchange

HardLow latencyMatching engineOrdering

Accept buy and sell orders, match them fairly in microseconds and publish trades to the market, like NASDAQ.

Functional requirements

  • Place, cancel and modify limit and market orders
  • Match orders by price, then time
  • Stream market data to subscribers

Non-functional requirements

  • Matching in microseconds
  • Strictly fair, first-come ordering
  • No order or trade is ever lost

Scale

  • 10K symbols
  • 1M orders per second at peak
  • Market data to 100K subscribers

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 stock exchange”, that starts with: Place, cancel and modify limit and market orders; Match orders by price, then time; Stream market data to subscribers. Interviewers notice candidates who pin the requirements down first.
  • Turn the scale into numbers. The scale (10K symbols; 1M orders per second at peak; Market data to 100K subscribers) 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: Matching in microseconds; Strictly fair, first-come ordering; No order or trade is ever 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 low latency, matching engine and ordering 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…