This package has been deprecated

Author message:

No longer maintained

rij

rij (pronounced "rye")

Safe and sensible work queue.

Rij is a Redis-backed Node.js module for reliabily processing and monitoring background tasks. Unlike Resque, DelayedJob, or Beanstalkd – each task within Rij is isolated to a process. That process can fail or even throw without the primary "management" process being affected or the job being lost. Failed tasks are provided back to the master process complete with a stack trace and attempted again by default.

Principles: Safety, Minimalism, Idempotence

Installation

npm install rij

Create A Worker

module.exports = function (job, callback) {
    callback(null, job.hello);
};

Enqueue A New Task

var rij = require('rij')();
 
rij.enqueue({
    worker: __dirname + '/path/to/worker.js',
    job:    {
        hello: 'world'
    }
}, function (err) {
    // Task has been added to the queue!
});

Start The Queue

var rij = require('rij')();
 
// Create the queue
var queue = rij.queue();
 
// Listen for events
queue.on('complete', function (msg) {
    // A task completed!
});
 
queue.on('incomplete', function (msg) {
    // Oh no! A task failed (but will be retried).
});
 
queue.on('fatal', function (err) {
    // Something really bad happened.
});

---

Methods

rij.enqueue - Enqueues a new task.

rij.queue - Starts workers.

Events

complete - Emitted when a task is completed successfully.

incomplete - Emitted when a task fails.

fatal - Emitted when a task fails fatally or when a critical issue is detected within Rij.

Configuration

Configuration and task defaults can be passed when requiring Rij:

var rij = require('rij')({
    namespace:      'rij',
    retry:          5,
    timeout:        10000,
    concurrency:    require('os').cpus().length,
 
    host:           '127.0.0.1',
    port:           6379,
    password:       null
});

Individual tasks can override the retry and timeout defaults. For example:

rij.enqueue({
    worker: __dirname + '/path/to/worker.js',
    job:    {
        hello: 'world'
    },
    retry: 10,
    timeout: 30000
}, function (err) {
    // Task has been added to the queue!
});

---

Differences to Resque

Before building Rij, DIY went through a number of background task systems including SQS, Beanstalkd and Resque. The differences between these three are fairly vast, but Rij is most similar to Resque most notability in the way in which both are backed by Redis and even more specifically Redis' list data type. From a feature standpoint both Resque and Rij provide: persistence, speed, distributed workers, and simple configuration. This really is where the similarities end however as Rij could be described as a rethink of Resque in both scope and approach within the Node.js ecosystem.

Resque is rather broad in it's scope. It provides many features which Rij does not including: tags, priorities, multiple queues, and even an entire Sinatra-based web app for monitoring, editing and managing queues. Rather Rij designed to be an incredibly light layer that sits in-between Redis and Node.js's cluster API that simply helps the user enqueue tasks, process them and provide feedback on status. Task editing and management interfaces are left up to user-land.