FIFO job queue backed by a pluggable Core.JobStore.

Each JobQueue is a GenServer that maintains an in-memory queue of job IDs and a map of job structs. Jobs are persisted via the store so they survive VM restarts (when using a durable backend such as Core.JobStore.SQLite).

Named queues

You can start multiple isolated queues by giving each a unique :name:

{Core.Workers.JobQueue, name: MyApp.EmailQueue, pool: MyApp.EmailPool}
{Core.Workers.JobQueue, name: MyApp.MediaQueue, pool: MyApp.MediaPool}

All public functions accept a server reference (atom or pid) as the first argument. The zero-arity versions operate on the default queue Core.Workers.JobQueue.

Options

• :name – registered name for this queue (default: Core.Workers.JobQueue)
• :pool – the WorkerPool name to notify when new jobs arrive
• :store – Core.JobStore module (default: Core.JobStore.Memory)
• :store_opts – options passed to the store's init/1
• :cleanup_interval_ms – how often to purge old jobs (default: 1 hour)
• :max_age_days – retention for completed / failed jobs (default: 7)

Worker notification

When a job is submitted (or a retry is scheduled), JobQueue calls notify_workers/1 which sends :work_available to every worker process under the configured WorkerPool. Workers use this as an immediate wake-up signal in addition to their fallback polling timer.