Job Queues

What it is

Job Queues take webhooks, mail, and retries off the page request. Zipper retries failed jobs. Poison messages go to a dead-letter queue. Payloads are AES-256-GCM and cannot sit in plaintext.

Cloudflare analogue: Cloudflare Queues. SLA 99.99% · p99 25ms. Operators create queues. Admins set retry policy.

• ▸Jobs retry
• ▸Dead-letter queue
• ▸AES-256-GCM payloads
• ▸Functions can consume

How it works

Producers enqueue JSON. Consumers pull with visibility timeout and retries. Payloads are AES-256-GCM at rest.

Failed payloads land in a dead-letter queue.

Use cases

Concrete ways teams use this service on day one.

Set it up in the dashboard

Dashboard → Services → Job Queues. Open a queue with consumer and retry counts.

API

Control-plane: GET|POST /api/v1/jobs/{id}/messages. Send Authorization: Bearer tz_live_YOUR_TOKEN.

Creates count against the plan quota. A 402 plan_limit means you are at the cap — upgrade or delete an unused resource.

curl -sS -X POST https://tinyzipper.com/api/v1/jobs \
  -H "Authorization: Bearer tz_live_YOUR_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"name":"webhooks","consumers":3,"retries":5}'

const res = await fetch("https://tinyzipper.com/api/v1/jobs/{id}/messages", {
  method: "GET",
  headers: {
    Authorization: `Bearer ${process.env.ZIPPER_TOKEN}`,
    "Content-Type": "application/json"
  }
});
const json = await res.json();
if (!res.ok) throw new Error(json.error ?? res.statusText);
console.log(json);

Tips

Visibility timeout must exceed the slowest consumer.

• ▸SOC 2
• ▸AES-256-GCM
• ▸At-least-once

Runbook

Size visibility timeout to the slowest consumer. Drain the dead-letter queue daily.