type: decision
status: active
timestamp: 2026-06-20
tags: [queue, cloudflare, workers, stack-cohesion]

Queue — Cloudflare Queues, picked for stack cohesion

Cloudflare Queues primary durable queue. Picked for native Worker bindings + same-account billing surface, not for feature richness. Upstash QStash + Inngest documented as deferred alternatives.

Queue — Cloudflare Queues, picked for stack cohesion

Decision

The family uses Cloudflare Queues as its sole durable message queue. The user direction was “unsure, no recommendation given” — this decision file records the reasoning behind the recommendation.

Upstash QStash and Inngest are documented as status: deferred alternatives if the primary’s quota cliff hits or the programming model becomes a constraint.

Why

The justification is stack cohesion, not feature richness:

QStash and Inngest each have feature edges (HTTP-from-anywhere, durable multi-step workflows respectively) but neither edge applies to current workloads, and both add a separate account, separate credentials surface, and an HTTP hop.

Implications

Cross-refs


Edit on GitHub · Back to index