agenda vs bee-queue vs bull vs bullmq vs kue
Node.js 任务队列库
agendabee-queuebullbullmqkue类似的npm包:

Node.js 任务队列库

任务队列库用于处理异步任务,允许开发者将任务放入队列中,并在后台处理这些任务。这些库通常用于处理需要延迟执行或需要高并发处理的任务,如发送电子邮件、处理图像或执行定时任务。它们提供了可靠的任务管理和调度机制,确保任务的顺序和成功执行。

npm下载趋势

3 年

GitHub Stars 排名

统计详情

npm包名称
下载量
Stars
大小
Issues
发布时间
License
agenda09,651297 kB27 天前MIT
bee-queue04,027107 kB464 个月前MIT
bull016,243309 kB1491 年前MIT
bullmq08,7052.45 MB3627 小时前MIT
kue09,459-2889 年前MIT

功能对比: agenda vs bee-queue vs bull vs bullmq vs kue

存储后端

  • agenda:

    Agenda 使用 MongoDB 作为存储后端,适合需要持久化和查询功能的应用。它可以存储任务的状态和调度信息,便于管理和监控。

  • bee-queue:

    Bee-Queue 使用 Redis 作为存储后端,提供高性能的任务队列,适合处理大量短任务。它的设计简单,易于使用。

  • bull:

    Bull 同样使用 Redis 作为存储后端,支持复杂的任务处理和调度,适合需要高并发和高可靠性的场景。

  • bullmq:

    BullMQ 也基于 Redis,提供更高级的功能和更好的性能,适合需要复杂任务管理的应用。

  • kue:

    Kue 使用 Redis 作为存储后端,提供简单的 API 和用户界面,适合需要快速实现任务队列的场景。

任务调度

  • agenda:

    Agenda 提供简单的任务调度功能,支持定时任务和周期性任务,适合需要定期执行的任务场景。

  • bee-queue:

    Bee-Queue 主要用于处理即时任务,不支持定时调度,适合需要快速处理的任务。

  • bull:

    Bull 提供丰富的任务调度功能,包括延迟任务、优先级和重试机制,适合复杂的任务处理需求。

  • bullmq:

    BullMQ 提供更高级的任务调度功能,支持工作流和事件驱动的任务处理,适合需要复杂调度的应用。

  • kue:

    Kue 提供基本的任务调度功能,支持优先级和失败重试,适合简单的任务处理场景。

监控与管理

  • agenda:

    Agenda 提供基本的监控功能,但缺乏图形化界面,适合开发者使用。

  • bee-queue:

    Bee-Queue 提供简单的监控功能,适合快速开发和调试。

  • bull:

    Bull 提供强大的监控和管理工具,可以实时查看任务状态,适合需要高可视化的应用。

  • bullmq:

    BullMQ 提供更高级的监控和管理功能,支持工作流监控,适合复杂应用的需求。

  • kue:

    Kue 提供直观的用户界面,可以实时监控任务状态,适合需要可视化管理的场景。

学习曲线

  • agenda:

    Agenda 的学习曲线较平缓,API 简单易懂,适合初学者使用。

  • bee-queue:

    Bee-Queue 的学习曲线也较平缓,设计简单,易于上手。

  • bull:

    Bull 的学习曲线稍陡,功能丰富,适合有一定经验的开发者。

  • bullmq:

    BullMQ 的学习曲线相对较陡,功能复杂,适合需要高级功能的开发者。

  • kue:

    Kue 的学习曲线较平缓,API 简单,适合快速实现任务队列的场景。

性能

  • agenda:

    Agenda 的性能依赖于 MongoDB 的性能,适合中小型应用。

  • bee-queue:

    Bee-Queue 具有极高的性能,适合处理大量短任务。

  • bull:

    Bull 性能优越,支持高并发任务处理,适合复杂应用。

  • bullmq:

    BullMQ 性能更强,适合需要更高吞吐量的应用。

  • kue:

    Kue 性能良好,适合中小型应用的任务处理。

如何选择: agenda vs bee-queue vs bull vs bullmq vs kue

  • agenda:

    选择 Agenda 如果你需要一个基于 MongoDB 的轻量级任务调度器,适合定时任务和周期性任务的管理,并且希望使用简单的 API 来处理任务调度。

  • bee-queue:

    选择 Bee-Queue 如果你需要一个快速且简单的任务队列,适合处理大量的短任务,并且希望利用 Redis 的高性能特性。

  • bull:

    选择 Bull 如果你需要一个功能丰富的任务队列,支持优先级、延迟和重试机制,适合复杂的任务处理场景,并且希望有良好的监控和管理工具。

  • bullmq:

    选择 BullMQ 如果你需要 Bull 的增强版,支持更高级的功能,如工作流和事件驱动的任务处理,适合需要更复杂的任务管理和调度的应用。

  • kue:

    选择 Kue 如果你需要一个简单易用的任务队列,支持优先级和失败重试,并且希望有一个直观的用户界面来监控任务状态。

agenda的README

Agenda

Agenda

A light-weight job scheduling library for Node.js

NPM Version NPM Downloads

Migrating from v5? See the Migration Guide for all breaking changes.

Agenda 6.x

Agenda 6.x is a complete TypeScript rewrite with a focus on modularity and flexibility:

  • Pluggable storage backends - Choose from MongoDB, PostgreSQL, Redis, or implement your own. Each backend is a separate package - install only what you need.

  • Pluggable notification channels - Move beyond polling with real-time job notifications via Redis, PostgreSQL LISTEN/NOTIFY, or other pub/sub systems. Jobs get processed immediately when saved, not on the next poll cycle.

  • Modern stack - ESM-only, Node.js 18+, full TypeScript with strict typing.

See the 6.x Roadmap for details and progress.

Features

  • Minimal overhead job scheduling
  • Pluggable storage backends (MongoDB, PostgreSQL, Redis)
  • TypeScript support with full typing
  • Scheduling via cron or human-readable syntax
  • Configurable concurrency and locking
  • Real-time job notifications (optional)
  • Sandboxed worker execution via fork mode
  • TypeScript decorators for class-based job definitions

Installation

Install the core package and your preferred backend:

# For MongoDB
npm install agenda @agendajs/mongo-backend

# For PostgreSQL
npm install agenda @agendajs/postgres-backend

# For Redis
npm install agenda @agendajs/redis-backend

Requirements:

  • Node.js 18+
  • Database of your choice (MongoDB 4+, PostgreSQL, or Redis)

Quick Start

import { Agenda } from 'agenda';
import { MongoBackend } from '@agendajs/mongo-backend';

const agenda = new Agenda({
  backend: new MongoBackend({ address: 'mongodb://localhost/agenda' })
});

// Define a job
agenda.define('send email', async (job) => {
  const { to, subject } = job.attrs.data;
  await sendEmail(to, subject);
});

// Start processing
await agenda.start();

// Schedule jobs
await agenda.every('1 hour', 'send email', { to: 'user@example.com', subject: 'Hello' });
await agenda.schedule('in 5 minutes', 'send email', { to: 'admin@example.com', subject: 'Report' });
await agenda.now('send email', { to: 'support@example.com', subject: 'Urgent' });

Official Backend Packages

PackageBackendNotificationsInstall
@agendajs/mongo-backendMongoDBPolling onlynpm install @agendajs/mongo-backend
@agendajs/postgres-backendPostgreSQLLISTEN/NOTIFYnpm install @agendajs/postgres-backend
@agendajs/redis-backendRedisPub/Subnpm install @agendajs/redis-backend

Backend Capabilities

BackendStorageNotificationsNotes
MongoDB (MongoBackend)Storage only. Combine with external notification channel for real-time.
PostgreSQL (PostgresBackend)Full backend. Uses LISTEN/NOTIFY for notifications.
Redis (RedisBackend)Full backend. Uses Pub/Sub for notifications.
InMemoryNotificationChannelNotifications only. For single-process/testing.

Backend Configuration

MongoDB

import { Agenda } from 'agenda';
import { MongoBackend } from '@agendajs/mongo-backend';

// Via connection string
const agenda = new Agenda({
  backend: new MongoBackend({ address: 'mongodb://localhost/agenda' })
});

// Via existing MongoDB connection
const agenda = new Agenda({
  backend: new MongoBackend({ mongo: existingDb })
});

// With options
const agenda = new Agenda({
  backend: new MongoBackend({
    mongo: db,
    collection: 'jobs'        // Collection name (default: 'agendaJobs')
  }),
  processEvery: '30 seconds', // Job polling interval
  maxConcurrency: 20,         // Max concurrent jobs
  defaultConcurrency: 5       // Default per job type
});

PostgreSQL

import { Agenda } from 'agenda';
import { PostgresBackend } from '@agendajs/postgres-backend';

const agenda = new Agenda({
  backend: new PostgresBackend({
    connectionString: 'postgresql://user:pass@localhost:5432/mydb'
  })
});

Redis

import { Agenda } from 'agenda';
import { RedisBackend } from '@agendajs/redis-backend';

const agenda = new Agenda({
  backend: new RedisBackend({
    connectionString: 'redis://localhost:6379'
  })
});

Real-Time Notifications

For faster job processing across distributed systems:

import { Agenda, InMemoryNotificationChannel } from 'agenda';
import { MongoBackend } from '@agendajs/mongo-backend';

const agenda = new Agenda({
  backend: new MongoBackend({ mongo: db }),
  notificationChannel: new InMemoryNotificationChannel()
});

Mixing Storage and Notification Backends

You can use MongoDB for storage while using a different system for real-time notifications:

import { Agenda } from 'agenda';
import { MongoBackend } from '@agendajs/mongo-backend';
import { RedisBackend } from '@agendajs/redis-backend';

// MongoDB for storage + Redis for real-time notifications
const redisBackend = new RedisBackend({ connectionString: 'redis://localhost:6379' });
const agenda = new Agenda({
  backend: new MongoBackend({ mongo: db }),
  notificationChannel: redisBackend.notificationChannel
});

This is useful when you want MongoDB's proven durability and flexible queries for job storage, but need faster real-time notifications across multiple processes.

API Overview

Defining Jobs

// Simple async handler
agenda.define('my-job', async (job) => {
  console.log('Processing:', job.attrs.data);
});

// With options
agenda.define('my-job', async (job) => { /* ... */ }, {
  concurrency: 10,
  lockLimit: 5,
  lockLifetime: 10 * 60 * 1000, // 10 minutes
  priority: 'high'
});

Defining Jobs with Decorators

For a class-based approach, use TypeScript decorators:

import { JobsController, Define, Every, registerJobs, Job } from 'agenda';

@JobsController({ namespace: 'email' })
class EmailJobs {
  @Define({ concurrency: 5 })
  async sendWelcome(job: Job<{ userId: string }>) {
    console.log('Sending welcome to:', job.attrs.data.userId);
  }

  @Every('1 hour')
  async cleanupBounced(job: Job) {
    console.log('Cleaning up bounced emails');
  }
}

registerJobs(agenda, [new EmailJobs()]);
await agenda.start();

// Schedule using namespaced name
await agenda.now('email.sendWelcome', { userId: '123' });

See Decorators Documentation for full details.

Scheduling Jobs

// Run immediately
await agenda.now('my-job', { userId: '123' });

// Run at specific time
await agenda.schedule('tomorrow at noon', 'my-job', data);
await agenda.schedule(new Date('2024-12-25'), 'my-job', data);

// Run repeatedly
await agenda.every('5 minutes', 'my-job');
await agenda.every('0 * * * *', 'my-job'); // Cron syntax

Job Control

// Cancel jobs matching a filter (removes from database)
await agenda.cancel({ name: 'my-job' });
await agenda.cancel({ name: 'my-job', data: { userId: 123 } });

// Cancel ALL jobs unconditionally
await agenda.cancelAll();

// Disable/enable jobs globally (by query)
await agenda.disable({ name: 'my-job' });  // Disable all jobs matching query
await agenda.enable({ name: 'my-job' });   // Enable all jobs matching query

// Disable/enable individual jobs
const job = await agenda.create('my-job', data);
job.disable();
await job.save();

// Progress tracking
agenda.define('long-job', async (job) => {
  for (let i = 0; i <= 100; i += 10) {
    await doWork();
    await job.touch(i); // Report progress 0-100
  }
});

Stopping / Draining

// Stop immediately - unlocks running jobs so other workers can pick them up
await agenda.stop();

// Drain - waits for running jobs to complete before stopping
await agenda.drain();

// Drain with timeout (30 seconds) - for cloud platforms with shutdown deadlines
const result = await agenda.drain(30000);
if (result.timedOut) {
    console.log(`${result.running} jobs still running after timeout`);
}

// Drain with AbortSignal - for external control
const controller = new AbortController();
setTimeout(() => controller.abort(), 30000);
await agenda.drain({ signal: controller.signal });

Use drain() for graceful shutdowns where you want in-progress jobs to finish their work.

Events

agenda.on('start', (job) => console.log('Job started:', job.attrs.name));
agenda.on('complete', (job) => console.log('Job completed:', job.attrs.name));
agenda.on('success', (job) => console.log('Job succeeded:', job.attrs.name));
agenda.on('fail', (err, job) => console.log('Job failed:', job.attrs.name, err));

// Job-specific events
agenda.on('start:send email', (job) => { /* ... */ });
agenda.on('fail:send email', (err, job) => { /* ... */ });

Custom Backend

For databases other than MongoDB, PostgreSQL, or Redis, implement AgendaBackend:

import { AgendaBackend, JobRepository } from 'agenda';

class SQLiteBackend implements AgendaBackend {
  readonly repository: JobRepository;
  readonly notificationChannel = undefined; // Or implement NotificationChannel

  async connect() { /* ... */ }
  async disconnect() { /* ... */ }
}

const agenda = new Agenda({
  backend: new SQLiteBackend({ path: './jobs.db' })
});

See Custom Backend Driver for details.

Documentation

Related Packages

Official Backend Packages:

Tools:

License

MIT