AllQ
  • What is AllQueue?
  • Getting Started
  • Install
    • Why AllQueue?
    • Architecture
    • 1. Install AllQueue Server
    • 2. Install AllQueue Client
    • Installation (Quick Start)
  • Foundational Concepts
    • Talking to AllQueue
    • Server/Client
    • Jobs
    • Tubes
    • Persistence
  • Features
    • Autobury Failed Jobs
    • Delayed Jobs/Scheduling
    • Priority
    • Workflow
    • Throttle
    • Fair Queuing
  • Configuration
  • Rest API Usage
  • Scenarios
  • Advanced
    • Docker Configuration Options
    • Federation Deployment
Powered by GitBook
On this page

Was this helpful?

  1. Foundational Concepts

Tubes

Named queue (also known is other queues as Topics or Groups)

A core concept of AllQ is the "tube".

A tube acts as a named queue where you can PUT jobs and GET jobs out of.

An example of tubes might be

  • emails_to_send

  • csv_loading

  • long_running_processes

When working with AllQ you will PUT a job into a tube, and then later GET a job out of a tube.

Tubes are created automatically when you PUT a job into one, and stats from the server will give you information about jobs stored within tubes.

Tubes can have the following actions performed on them

  • Throttle (sets max TPS on tube)

  • Pause (sets TPS=0 on tube, pausing workers from getting jobs)

  • Drain (only allow outbound jobs, won't accept inbound ones)

PreviousJobsNextPersistence

Last updated 5 years ago

Was this helpful?