Starter example Bindings

A small Queues example you can adapt quickly

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'

}

]

}

})

Then use it in one honest runtime path

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'

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()

}

Lock in the behavior with one small test or smoke path

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.

A direct consumer test

import { afterAll, beforeAll, expect, test } from 'bun:test'

import { createTestContext, cf } from 'devflare/test'

import { env } from 'devflare'

beforeAll(() => createTestContext())

afterAll(() => env.dispose())

test('queue work writes a result record', async () => {

await cf.queue.trigger([{ id: 'msg-1', body: { id: 'job-1' } }])

expect(await env.RESULTS.get('job:job-1')).toBe('done')

})

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.

AI

AI is a supported binding in Devflare, but it is intentionally treated as remote-oriented because real model inference lives on Cloudflare infrastructure.