Background jobs with a queue
FreeSystem map@rabbinatix/background-jobs-architecture by Rabbinatixupdated Oct 13, 2026
Slow work leaves the request: the backend puts a job on a queue, a worker does it, stores the file and emails a link.
6 systems and 7 APIs. Every API is declared on both sides, so every contract starts healthy. Rename or change anything once it is on your map.
6 connections · 7 APIs
- Web App → Backend API
POST /api/v1/exportsAsk for an exportGET /api/v1/exports/{id}How an export is going
- Backend API → Job Queue
POST /queues/exports/messagesQueue an export job
- Export Worker → Job Queue
GET /queues/exports/messagesTake the next job
- Export Worker → Backend API
PATCH /internal/v1/exports/{id}Report a job’s progress
- Export Worker → File Storage
PUT /{bucket}/{key}Upload the file
- Export Worker → Email API
POST /v3/mail/sendEmail the download link
Systems (6)
Web App
Where people ask for an export.
Backend API
Takes the request and queues the job.
Job Queue
Holds jobs until a worker picks them up.
Export Worker
Builds the export file.
File Storage
Keeps the files, like S3 or Cloud Storage.
Email API
Sends the “your export is ready” email.
A system you already have under the same name is used, not copied. Outside APIs don't count towards your plan.
Versions
