Design: an object store (S3)

The core idea

An object store gives an application a name for a completed file and a way to retrieve its bytes.

We'll design one for exported reports: an upload may take minutes, but readers must never see a half-written report.

In this lesson

  • Names, permissions and visible state
  • Keep ownership separate from byte transfer
  • Upload a report without holding a database lock
  • Cancellation must exclude later publication
  • Resolve once, then read the selected bytes
  • Partition names without concentrating all their bytes
  • Storage cost includes the next failure
  • Run the publication boundary locally

Continue reading

Pro unlocks video lessons, visual walkthroughs, full notes, diagrams, case studies, and implementations across the System Design archive.