← Back to Labs

Object Storage Commit Path

Trace one multipart upload from auth and placement to erasure-coded shards, manifest publish, range reads, and background healing.

clientuploaderdemo.mp4front doorAPI / ingressauth, checksum, multipartcontrol planemetadatakey, version, placementpending upload onlyerasure setd0idled1idled2idled3idled4idled5idlep0idlep1idleserve + healreader stateGET still returns the old object or not foundobj
Step 1 / 6The API layer authenticates the caller and opens an upload session

The object is not durable just because the first bytes arrived. The frontend first checks bucket policy, opens a multipart upload session, and reserves namespace state without making a new object visible yet.

API: PUT /media/demo.mp4 authorised, uploadId u-73 created
Metadata: key reserved in metadata, no committed version yet
Manifest: manifest unpublished
Repair: no shard placement yet

Arrow keys to navigate · R to reset

Tap dots to jump to any step

Read the full article →Take the quiz →