uploadput objectsave metadataClientAPI gatewayUpload functionObject storageMetadata DB
Architectureblueprint

Serverless File Upload

A serverless upload path: client, API gateway, an upload function, object storage, and a metadata database.

Start from this template

Opens in the editor. No signup. Export SVG, PNG, or an embed link.


Source text
title: Serverless File Upload
theme: blueprint
node client "Client" [client]
node gw "API gateway" [gateway]
node fn "Upload function" [function]
node bucket "Object storage" [storage]
node meta "Metadata DB" [database]
gw right-of client
fn right-of gw
bucket right-of fn
meta below fn
client -> gw : "upload" flow
gw -> fn
fn -> bucket : "put object"
fn -> meta : "save metadata"

About this template

A serverless upload path: the client uploads through an API gateway to an upload function. The function puts the file into object storage and saves its metadata (name, size, owner) in a database.

It fits serverless or managed-service designs, where the interesting part is how a few managed pieces connect. Function and storage icons make the managed parts easy to spot.

A common variation is a direct upload with a pre-signed URL: draw "client -> bucket : "pre-signed PUT"" and have the function only issue the URL and save the metadata.