agenda vs bree vs bull vs cron vs later vs node-cron vs node-schedule
Node.js 定时任务库
agendabreebullcronlaternode-cronnode-schedule类似的npm包:

Node.js 定时任务库

定时任务库用于在 Node.js 中调度和执行定时任务。这些库提供了不同的功能和灵活性,帮助开发者在特定时间或间隔执行任务。它们适用于需要定期执行的任务,如发送电子邮件、清理数据库、生成报告等。选择合适的库可以提高应用程序的效率和可维护性。

npm下载趋势

3 年

GitHub Stars 排名

统计详情

npm包名称
下载量
Stars
大小
Issues
发布时间
License
agenda09,662297 kB42 天前MIT
bree03,28692 kB293 个月前MIT
bull016,243309 kB1491 年前MIT
cron08,927161 kB305 个月前MIT
later02,417-9811 年前MIT
node-cron03,255221 kB3610 个月前ISC
node-schedule09,21035 kB1713 年前MIT

功能对比: agenda vs bree vs bull vs cron vs later vs node-cron vs node-schedule

持久化任务

  • agenda:

    Agenda 提供了持久化任务的功能,任务信息存储在 MongoDB 中,确保任务在应用重启后仍然存在。适合需要高可靠性的任务调度。

  • bree:

    Bree 不支持持久化任务,任务在内存中执行,适合轻量级和短期任务。

  • bull:

    Bull 支持持久化任务,任务信息存储在 Redis 中,确保任务的可靠性和持久性。

  • cron:

    Cron 不支持持久化任务,适合简单的定时任务,任务信息在内存中。

  • later:

    Later 不支持持久化任务,适合短期任务和简单调度。

  • node-cron:

    Node-Cron 不支持持久化任务,适合轻量级的定时任务。

  • node-schedule:

    Node-Schedule 不支持持久化任务,适合灵活的调度需求。

调度灵活性

  • agenda:

    Agenda 提供了丰富的调度选项,支持重复任务、延迟任务和复杂的调度逻辑,适合复杂的应用场景。

  • bree:

    Bree 提供简单的调度选项,适合快速开发和简单任务。

  • bull:

    Bull 提供了优先级和延迟任务的支持,适合需要处理大量任务的应用。

  • cron:

    Cron 使用类 Unix 的 cron 表达式,适合简单的定时任务。

  • later:

    Later 提供了灵活的调度选项,支持多种时间格式,适合高度自定义的调度需求。

  • node-cron:

    Node-Cron 提供简单的 cron 风格调度,适合小型应用。

  • node-schedule:

    Node-Schedule 支持 cron 表达式和日期对象,适合多种调度需求。

性能

  • agenda:

    Agenda 性能依赖于 MongoDB 的性能,适合需要高可靠性的任务调度。

  • bree:

    Bree 使用 worker 线程执行任务,适合 CPU 密集型任务,性能优越。

  • bull:

    Bull 基于 Redis,提供高性能的任务队列,适合处理大量任务。

  • cron:

    Cron 性能良好,适合简单的定时任务。

  • later:

    Later 性能适中,适合短期任务和简单调度。

  • node-cron:

    Node-Cron 性能良好,适合轻量级的定时任务。

  • node-schedule:

    Node-Schedule 性能适中,适合灵活的调度需求。

易用性

  • agenda:

    Agenda 提供了简单的 API,易于上手,适合新手和快速开发。

  • bree:

    Bree API 简洁,易于使用,适合快速开发。

  • bull:

    Bull 提供了丰富的功能,可能需要一定的学习成本,但文档清晰。

  • cron:

    Cron API 简单,易于理解,适合小型项目。

  • later:

    Later API 灵活,适合需要自定义调度的开发者。

  • node-cron:

    Node-Cron API 简单,易于使用,适合新手。

  • node-schedule:

    Node-Schedule API 灵活,适合多种调度需求,学习曲线适中。

社区支持

  • agenda:

    Agenda 拥有活跃的社区和良好的文档支持,适合需要社区帮助的开发者。

  • bree:

    Bree 社区相对较小,但文档清晰,适合快速开发。

  • bull:

    Bull 拥有强大的社区支持和丰富的文档,适合需要帮助的开发者。

  • cron:

    Cron 社区活跃,文档简单易懂,适合新手。

  • later:

    Later 社区较小,但文档清晰,适合自定义调度的开发者。

  • node-cron:

    Node-Cron 社区活跃,文档简单,适合新手。

  • node-schedule:

    Node-Schedule 拥有活跃的社区和良好的文档支持,适合需要社区帮助的开发者。

如何选择: agenda vs bree vs bull vs cron vs later vs node-cron vs node-schedule

  • agenda:

    选择 Agenda 如果你需要一个基于 MongoDB 的任务调度库,适合需要持久化任务和复杂调度的场景。它支持重复任务和延迟任务,非常适合需要高可靠性的应用。

  • bree:

    选择 Bree 如果你需要一个轻量级的任务调度库,支持使用 worker 线程来执行任务,适合 CPU 密集型任务。它简单易用,适合快速开发和小型项目。

  • bull:

    选择 Bull 如果你需要一个高性能的任务队列,支持优先级、延迟和重试机制,适合需要处理大量任务的应用。它基于 Redis,提供了强大的功能和良好的性能。

  • cron:

    选择 Cron 如果你需要一个简单的定时任务调度器,支持类 Unix 的 cron 表达式,适合简单的定时任务。它易于使用,适合小型项目和简单的调度需求。

  • later:

    选择 Later 如果你需要一个灵活的定时任务调度库,支持复杂的调度逻辑和多种时间格式。它适合需要高度自定义的调度需求。

  • node-cron:

    选择 Node-Cron 如果你需要一个轻量级的 cron 风格的调度库,易于使用且不依赖外部存储。它适合简单的定时任务,适合小型应用。

  • node-schedule:

    选择 Node-Schedule 如果你需要一个功能丰富的调度库,支持复杂的时间规则和日期,适合需要灵活调度的应用。它支持 cron 表达式和日期对象,适合多种调度需求。

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) => { /* ... */ });

Use fail listeners to capture richer error context, such as stack traces, without storing large payloads in job.attrs.failReason:

agenda.on('fail', async (err, job) => {
	await saveJobError({
		jobId: job.attrs._id,
		jobName: job.attrs.name,
		message: err.message,
		stack: err.stack
	});
});

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