ADR-006 — Job Processing

Status

Accepted for V1.

Context

Raster tiling, detection, segmentation, QA, and exports can take longer than a normal HTTP request.

Decision

Use Redis + RQ for V1 background jobs. Every long-running operation creates an analysis_run or job record, updates status, stores outputs, and emits events.

Supported statuses:

pending,
queued,
running,
completed,
failed,
cancelled.

Consequences

The UI can show progress and status without blocking. RQ is easier than Celery for an initial solo/portfolio project.

Non-goals

No Kubernetes-native queues, no Airflow, no full workflow engine in V1.

654 B Raw Blame History