Application example Bindings

Use Queues in a real application path

Queues let Workers send messages to background consumers with retries, batching, and dead-letter handling.

This starter example wires one producer, one consumer, and one stored result so you can see the whole queue loop without ceremony.

A good queue example should prove three things quickly: the request can enqueue work, the consumer can process it, and some visible side effect confirms the work ran.

Config focus: Explicit producer and consumer config
Runtime shape: Request enqueues work, queue handler stores result
Best use: Background jobs and post-request processing

Start by wiring the binding clearly in config

Minimal queue config

import { defineConfig } from 'devflare/config'

export default defineConfig({

name: 'queue-example',

bindings: {

kv: {

RESULTS: 'results-kv'

queues: {

producers: {

JOBS: 'jobs-queue'

consumers: [

{

queue: 'jobs-queue'

}

]

}

})

Build the application flow around the binding

Treat this as the app-level Queues path: the route, event handler, or service module receives a real request and uses the binding to do useful work.

Keep product limits, remote ownership, and fallback behavior visible in the code around the binding instead of hiding everything behind a vague utility too early.

Once this shape works, you can add retries, DLQs, and richer payloads without changing the fundamental loop.
This example stays intentionally small so the queue contract is the thing you notice first.

One fetch path and one queue consumer

import { env } from 'devflare/runtime'

import type { MessageBatch } from '@cloudflare/workers-types'

export async function fetch(): Promise<Response> {

await env.JOBS.send({ id: 'job-1', createdAt: Date.now() })

return new Response('queued', { status: 202 })

}

export async function queue(batch: MessageBatch<{ id: string }>): Promise<void> {

for (const message of batch.messages) {

await env.RESULTS.put('job:' + message.body.id, 'done')

message.ack()

}

Keep production boundaries visible

Config focus: Explicit producer and consumer config.
Runtime shape: Request enqueues work, queue handler stores result.
Best use: Background jobs and post-request processing.

Keep the first side effect visible

Writing one result record is a better first example than a complex job pipeline you cannot see end to end.

Testing Queues

Queue testing is one of the places where Devflare’s helper surface feels especially good because the queue trigger already knows how to drive the real handler shape.

Services

The fast Devflare payoff is simple: wire one worker to another with , call it through , and prove the same relationship locally in one test.