Design of a Blob Store

The blob store separates metadata decisions from bulk data transfer. Follow one upload through chunk placement and commit, then use that distinction to reason about reads, retries, and deletion.

High-level design

A blob store system consists of three core components: clients, frontend servers, and storage disks.

Frontend servers receive client requests and store blobs on attached storage disks.

API design

These logical operations assume an authenticated account. Check authorization for the named container or blob on each request; a valid account is not permission to access every object. Public reads are a separate access-policy case.

Create container

The createContainer operation creates a new container under the current user’s account.

createContainer(containerName)