Question 1

How to schedule a job to run later in node-resque?

Accepted Answer

Use the queue.enqueueIn() or queue.enqueueAt() methods to delay job execution. For example, await queue.enqueueIn(3000, 'math', 'subtract', [2, 1]) schedules a job to run after 3 seconds, as shown in the usage example.

Question 2

Node-resque vs Bull: which should I use for background jobs?

Accepted Answer

Node-resque is better if you need API compatibility with Ruby's Resque or want a feature-rich system with plugins and MultiWorker. Bull offers a more modern API with rate limiting, but node-resque excels in cross-platform reliability and proven patterns.

Question 3

How do I handle failed jobs in node-resque?

Accepted Answer

Failed jobs are moved to a special failed queue. You can inspect them with queue.failed(), retry them with queue.retryAndRemoveFailed(), or manually manage them using methods described in the Failed Job Management section.

Question 4

Can I run multiple workers on one server with node-resque?

Accepted Answer

Yes, use the MultiWorker class, which auto-scales workers based on CPU load. Configure minTaskProcessors and maxTaskProcessors to control the pool size, as detailed in the MultiWorker options.

Question 5

What plugins come with node-resque?

Accepted Answer

Included plugins are DelayQueueLock, JobLock, QueueLock, and Retry, which help prevent duplicate jobs and handle retries automatically. You can also write custom plugins by extending the Plugin class, as explained in the Plugins section.

Question 6

How to monitor job progress in node-resque?

Accepted Answer

Use the event system; workers emit events like 'start', 'success', 'failure', etc. Attach listeners to these events to track job execution in real-time, with examples provided in the code snippet.

node-resque

What is node-resque?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Open Source Alternative To

Frequently Asked Questions