# Jobs stay on the template's Postgres lease queue

The repository's architectural decision, rationale and consequences.

# Jobs stay on the template's Postgres lease queue

The ARD (product ADR-04) chose pg-boss for link reading, OCR, trip estimates and the catalogue refresh. The template already runs leased jobs in Postgres through Drizzle and a one-minute cron tick (ADR-0005, ADR-0006), which gives the same "one database, no extra broker" property. We use it instead of adding pg-boss (needs a long-lived Node process Workers do not have) or Cloudflare Queues (a second system to operate and observe). Throughput ceiling is the cron cadence; acceptable for v1 volumes (RNF04 needs ≤ 10 s per import, so imports are processed inline on request and only retried by the queue).

