Queues

Queues gives Workers a native way to decouple work. Producers push messages and consumers process them in batches, with automatic retries and dead-letter queues. It is pleasant and cheap for “do this expensive thing later,” and exposing a queue as another binding feels right.

Its limitations set a low ceiling. Per-queue throughput caps push you towards sharding, there is no FIFO ordering, and at-least-once delivery leaves duplicate handling to you. It also runs on Durable Objects, which does not reassure me about tail latency or availability.

It’s a happy fit for webhooks, notifications, and background processing where a delayed or duplicate message is harmless. I would not put it at the center of an event-driven architecture yet.