← Back to Labs

Queue-Backed Job System

Follow one background job from durable handoff to lease, crash, replay-safe retry, dead-letter handling, and backlog monitoring.

APIJobs DBReady queueWorker AWorker BSide effectDLQjob-9812The request path commits durable job intent before replyingDurable handoff is the real boundary, not the HTTP response.attempt-job statequeued in jobs tableleasenot leased yetside effectnothing external has happened
Ready
0
Running
0
Retries
0
Completed
0
Dead-letter
0
Step 1 / 9The request path commits durable job intent before replying

The API accepts one export request and writes a real job record first. Returning a job id before that write would mean the user sees accepted work that the system might lose on crash.

Arrow keys to navigate · R to reset

Tap dots to jump to any step

Read the full article →Take the quiz →