Stupid simple distributed job scheduling in node, backed by redis.

Bossbat combines schedulers and workers into a single concept, which aligns better with most node applications. All of the jobs run with a redis lock, preventing more than once instance from performing a given job at a time.

Bossbat is published on npm, and can be installed simply:

npm install bossbat --save

Or if you use Yarn in your project:

yarn add bossbat

You can then import the module and use it normally. For more details, see the API documentation.

import Bossbat from 'bossbat';

// Make sure you name your variables clever things:
const fred = new Bossbat({
  connection: {
    host: '127.0.0.1',
    port: 6379,
  },
  // Set the redis key prefix:
  prefix: 'bossbat:',
});

// Hire for a job.
fred.hire('engineers', {
  every: '10 minutes',
  work: () => {
    // Do something...
  },
});

// Hire something as soon as possible:
fred.demand('engineers');

// You can also "qa" work:
fred.qa((jobName, jobDefinition, next) => {
  return next();
});

// Fire a job, this will cancel any pending jobs:
fred.fire('engineers');

// Shut down our instance.
fred.quit();

Creates a new bossbat instance. All arguments are optional.

• options.connection: Used to configure the connection to your redis. This accepts the same arguments that ioredis does.
• options.prefix: A string that all redis keys will be prefixed with. Defaults to bossbat.
• options.ttl: The number of milliseconds before a job times out. Setting it will change the maximum duration that jobs can hold a lock. By default, job locks will timeout if a job does not complete in 2000ms.
• options.tz: An optional timezone used with jobDefinition.cron expressions.
• options.disableRedisConfig: Disable usage of the redis CONFIG command, as it might be disabled in certain redis configurations. NOTE: If this option is used, the redis configuration should contain notify-keyspace-events Ex

Schedules recurring work to be done.

• jobName: A unique name for the job.
• jobDefinition: The job definition can contain three properties: work, every, and cron.
  • jobDefinition.work: A function that is invoked to perform the job. If the work is async, this function should return a promise to properly reflect the completion of the job.
  • jobDefinition.every: A string which describes the interval the job will be run. This can either be a human-friendly string (which will be parsed by the timestring module), or a number reflecting the milliseconds to wait between each job run.
  • jobDefinition.cron: A string used to schedule work in more complex intervals. These are parsed with cron-parser.

It's possible to omit the every or cron properties if you don't wish to schedule recurring work, and just want to register a job.

Runs a job as soon as possible, outside of the scheduled jobs. Demanded jobs still run with the same locking mechanism that scheduled jobs run with, ensuring only one instance runs the job at a time. This does not prevent any scheduled jobs from running, unless the demand is running at the same time as a scheduled job and all instances fail to acquire a lock on the job.

QA is used to register functions that will be invoked any time a job is run. This function can be called multiple times to register multiple QA functions. The passed qaFunction function will be called with jobName, and jobDefinition from the hire function, as well as a next function, which should be called when the QA function is complete. The next function returns a promise that can be used to run code after a job is completed.

For example, here is what a time logging QA function might look like.

bossbat.qa((jobName, jobDefinition, next) => {
  const startTime = Date.now();
  return next().then(() => {
    const endTime = Date.now();
    logToServer(`${jobName} completed in ${endTime - startTime}ms`);
  })
});

Cancels any scheduled jobs with name jobName. This does not stop any demanded jobs from running.

Shuts down a bossbat instance, closing all redis connections. This does not cancel any scheduled work, and does not stop it from running in any other bossbat instances.

Constructing a new bossbat instance sets up an expired key listener on your redis database. When you hire for a new job, Bossbat sets a key in Redis that expire when the first run should occur. When the key expires, the expired key listener is called and Bossbat does the following:

1. Attempt to get a lock to perform the work. Only one instance of bossbat will acquire the lock.
2. If the lock is acquired, then perform the work and move on.
3. If the lock is not acquired, then move on.
4. Schedule the next run of the job by setting a key that expires when the next run should occur.

It's worth noting that every instance of Bossbat attempts to schedule the next run of the job. This is okay because Redis will only schedule the first one that it receives, thanks to the NX option in SET. Calling demand performs the same operation as hire, except with a special key for demands.