BullMQ Proxy
  • What is BullMQ Proxy
  • Getting started
    • Architecture overview
    • Using Dragonfly
  • HTTP API
    • Authentication
    • Queues
      • Adding jobs
        • Retries
        • Delayed jobs
        • Prioritized
        • Repeatable
        • LIFO
        • Custom Job IDs
      • Getting jobs
      • Queue's actions
      • Reference
    • Workers
      • Endpoints
      • Adding workers
        • Concurrency
        • Rate-Limit
        • Removing finished jobs
        • Stalled jobs
        • Timeouts
      • Removing workers
      • Getting workers
      • Reference
    • Jobs
      • Jobs' actions
        • Update job progress
        • Add job logs
      • Reference
    • Configuration
    • Debugging
Powered by GitBook
On this page
  1. HTTP API

Queues

Queues are recipients of jobs (also called messages in other systems), a BullMQ Proxy can contain any number of queues, all sharing the same Redis instance. For practical purposes, the number of queues should be kept low, even though they are lightweight and do not consume CPU if they are not being used.

Queues can be found on the /queues endpoint. There are a number of operations that are provided in this endpoint which we will cover in the next sub pages.

PreviousAuthenticationNextAdding jobs

Last updated 1 year ago