Problem Understanding
Restate the problem in your own words.
Design a Distributed File System (S3 / HDFS)
Design an S3 / HDFS-class distributed file system: clients PUT and GET objects of any size (KB to TB), grouped into buckets, with strong read-after-write consistency on new keys, 11-nines durability, and per-client throughput in the GB/s for large objects. The architecture splits cleanly into a metadata service (small, hot, strongly consistent — it knows where every chunk of every object lives) and a data plane (massive, chunked storage spread across thousands of nodes with 3-way replication or erasure coding). The hard decisions are chunk size, replication topology, metadata sharding strategy, and multi-region durability vs cost.
- Amazon S3The category-defining cloud object store; trillions of objects; foundational to AWS.
- Google Cloud Storage / GCSGoogle's analogue; multi-region built-in.
- Azure Blob StorageMicrosoft's; hot / cool / archive tiers from day one.
- HDFS / MinIO / CephOn-prem / open-source flavours; same chunk-and-replicate shape.
Your task: read the problem above, then write what the system is, who uses it, the rough scale, and the headline UX expectation — in your own words. Submit for AI review when you're ready.
Click any step in the sidebar to jump around — sections don't have to be done in order. Press ? any time to see all shortcuts.