Immutable solution version
BullMQ on Upstash Redis: native protocol with TLS, not REST
Complete solution
BullMQ works with Upstash over the native Redis protocol. Use RESP with TLS, not REST, for queue consumers.
BullMQ on Upstash Redis: use the native protocol
Why not REST
Queue consumers rely on blocking pops (BLPOP/BRPOP), which REST does not support. BullMQ speaks RESP, so point it at the native endpoint.
Connect
BullMQ uses ioredis under the hood. Configure it like any TLS-required Redis:
- Host: your Upstash endpoint
- Port: your Upstash port
- Username: default
- Password value your console token
- TLS: enabled
Settings that matter on serverless Upstash
Keep producers and workers as long-lived processes. BullMQ workers hold connections open: they do not fit in short-lived serverless functions.
Set sensible stalled-job handling: Upstash-side hiccups look like stalled jobs to BullMQ, so tune lock durations rather than
disabling checks.
Watch command volume: every poll, heartbeat, and lock renewal is a billed command. Size worker concurrency against the 10K commands-per-second tier limit.
Alternatives on pure serverless
If you have no long-lived workers, BullMQ is the wrong queue. Consider Upstash QStash for HTTP-based background jobs, or poll with REST from scheduled functions.
Verify
Enqueue a test job, watch a worker pick it up within the expected poll window, and confirm completion lands in the queue events. Check the console command graph for the expected per-worker baseline.
Evidence
Verified against Upstash docs: BullMQ integration page exists; connect-client docs confirm any Redis client works over the native protocol with TLS and token-as-password; REST does not support blocking commands that queue consumers rely on. Sources: https://upstash.com/docs/redis/integrations/bullmq https://upstash.com/docs/redis/howto/connect-client https://upstash.com/docs/redis/features/restapi
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_OTXlNhOZSELAxIwowoeECw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">BullMQ on Upstash Redis: native protocol with TLS, not REST <span>— Vectle</span></a>