Vercel Queues now in public beta

Vercel Queues is a durable event streaming system built with Fluid compute, and is now available in public beta for all teams. Vercel Queues also powers Workflow: use Queues for direct message publishing and consumption, Workflow for ergonomic multi step orchestration.

Functions need a reliable way to defer expensive work and guarantee that tasks complete even when functions crash or new deployments roll out. Queues makes it simple to process messages asynchronously with automatic retries and delivery guarantees, providing at-least-once delivery semantics.

How it works:

• Messages are sent to a durable topic

• The queue fans messages out to subscribed consumer groups.

• Each consumer group processes messages independently.

• The queue redelivers messages to consumer groups until successfully processed or expired.

Publish messages from any route handler:

1
import { send } from '@vercel/queue';
2
 
3
export async function POST(request: Request) {
4
  const order = await request.json();
5
  const { messageId } = await send('orders', order);
6
  return Response.json({ messageId });
7
}

Create a consumer:

1
import { handleCallback } from '@vercel/queue';
2
 
3
export const POST = handleCallback(async (order, metadata) => {
4
  console.log('Fulfilling order', metadata.messageId, order);
5
  // await doAnythingAsync(order);
6
});

Configure the consumer group:

1
{
2
  "functions": {
3
    "app/api/queues/fulfill-order/route.ts": {
4
      "experimentalTriggers": [{ "type": "queue/v2beta", "topic": "orders" }]
5
    }
6
  }
7
}

Adding a trigger makes the route private: it has no public URL and only Vercel's queue infrastructure can invoke it.

Vercel Queues is billed per API operation, starting at $0.60 per 1M operations, and includes:

• Multiple AZ synchronous replication

• At-least-once delivery

• Customizable visibility timeout

• Delayed delivery

• Idempotency keys

• Concurrency control

• Per-deployment topic partitioning

Functions invoked by Queues in push mode are charged at existing Fluid compute rates.

Get started with the Queues documentation.