ScaleCrafts

Design an object storage service

HardDurabilityErasure codingMetadata

Store and retrieve any amount of data as objects in buckets with extreme durability, like Amazon S3.

Functional requirements

  • PUT, GET and DELETE objects in buckets
  • Objects from a few bytes to 5 TB
  • List objects by prefix

Non-functional requirements

  • Eleven nines of durability
  • High availability across data centers
  • Strong read-after-write consistency

Scale

  • 100 trillion objects
  • Exabytes of data
  • Millions of requests per second

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 an object storage service”, that starts with: PUT, GET and DELETE objects in buckets; Objects from a few bytes to 5 TB; List objects by prefix. Interviewers notice candidates who pin the requirements down first.
  • Turn the scale into numbers. The scale (100 trillion objects; Exabytes of data; Millions of requests per second) 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: Eleven nines of durability; High availability across data centers; Strong read-after-write consistency. 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 durability, erasure coding and metadata 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.

Loading your workspace…