Presenter mode

Object vs block vs file

Full page · Paths

Walkthrough

Object put/get path

Illustrative object API: client/SDK → front → metadata + durable nodes. S3 product docs define the interface; internal node maps stay unknown.

Step 1 / 4
PUT / GET objectApp / SDKObject API frontMetadataObject nodes

The application issues an object put/get via the HTTP/API surface (Amazon S3 storage-classes product docs). This is an opaque blob contract — not a mounted disk.

Walkthrough

Block volume attach

Illustrative EBS-class path: VM → attach plane → block volume, with snapshot as a separate durability action.

Step 1 / 3
AttachVM instanceVolume attachBlock volumeSnapshot store

A VM attaches a block volume as a disk (Amazon EBS product docs). Failure domains differ from object put/get — the guest sees a block device.

Walkthrough

Replication vs erasure coding (illustrative)

Teaching walkthrough of full-copy replication vs (k, m) EC overhead. Calculator is illustrative — never claim these parameters are S3/GCS/Azure Blob internals.

Step 1 / 4
WriteWriterPlacement controlReplica / shard AReplica / shard BReplica / shard C

Placement control spreads durable copies or shards. GFS-era designs emphasize chunk replication; Dynamo publishes configurable N — separate eras and systems.