Skip Proposed · Cloudflare

Cloudflare Queues

Fine when producer and consumer are both Workers. Inside AWS, SQS wins.

Proposed verdict: drawn from research, not yet confirmed by Nic.

No FIFO, no IAM, no Lambda back-pressure, and ten times SQS's cost at volume. I don't need it.

Use it when

  • Both ends run on Workers, or you need delays longer than 15 minutes.

Don't use it when

  • Anything inside AWS. SQS has FIFO, IAM and batched Lambda consumers.

Pricing

$0.40 per million operations (each write, read and delete; about 3 per message), billed per message so batching saves nothing. 50M messages ≈ $60 vs about $6 on SQS batched.

Gotchas, with fixes

Gotcha: Without a dead-letter queue, failed messages are deleted.

Fix: Always configure a DLQ.

Provisioning

Official Pulumi package · Official Terraform provider

Use instead

SQS: FIFO, IAM and batched Lambda consumers, inside AWS where the work is.

Alternatives

Sources

Last reviewed by Nicolas Dao

Want this stack in your AWS account?

Cloudless Labs is a Sydney consultancy. We migrate on-premises systems to AWS, build serverless apps on this stack, and coach teams to ship with Claude Code and Codex.

Contact Us

For general inquiries, please contact us at:

For e-learning capabilities, please contact: