Rabbinatix
Sign inGet started
Store

File uploads and media processing

FreeSystem map
@rabbinatix/file-uploads-architecture by Rabbinatixupdated Oct 13, 2026

Files go straight to storage with a signed link; a worker scans and resizes each one, and the app shows it once it is ready.

6 systems and 11 APIs. Every API is declared on both sides, so every contract starts healthy. Rename or change anything once it is on your map.

As the map's Connections view shows it: traffic flows from the system that calls to the system it calls.

6 connections · 11 APIs

  • Web App → Files API
    • POST/api/v1/auth/registerCreate an account
    • POST/api/v1/auth/loginLog in with email and password
    • POST/api/v1/auth/logoutLog out
    • POST/api/v1/uploadsAsk for an upload link
    • POST/api/v1/uploads/{fileId}/completeSay the upload finished
    • GET/api/v1/files/{fileId}A file and its versions
  • Web App → Object Storage
    • PUT/{bucket}/{key}Upload the file with the signed link
  • Files API → Job Queue
    • POST/queues/media/messagesQueue a file for processing
  • Media Worker → Job Queue
    • GET/queues/media/messagesTake the next file
  • Media Worker → Virus Scanner
    • POST/v1/scanScan a file
  • Media Worker → Files API
    • PATCH/internal/v1/files/{fileId}Report the result

Systems (6)

Web App
Where people upload and view files.
Files API
Gives out upload links and keeps each file’s record.
Job Queue
Files waiting to be processed.
Media Worker
Scans for viruses, makes thumbnails and smaller versions.
Object Storage
Keeps the files, like S3 or Cloud Storage.
Virus Scanner
Checks a file is safe, like ClamAV or a scanning API.

A system you already have under the same name is used, not copied. Outside APIs don't count towards your plan.

Also as a flow

Versions