Skip to content
ironflow
Ironflow is pre-1.0: APIs can change between releases. Pin a version. What is ready →

File Storage

A file write touches two stores and one event path. The service writes the bytes to the blob backend first, then commits the catalog row and its event row in one transaction, then dispatches the event to matching functions. The event sweeper covers a crash between commit and dispatch. The retirement cleanup deletes the bytes of an overwritten or deleted file.

Ironflow file storage architecture: SDK, REST, files service, catalog, blob backend, event sweeper, retirement cleanup and functions

For the model, limits and consistency rules, see File Storage. The two flows are Signed URL Flow and File Event Flow.