npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

decent

v1.0.1

Published

This is a decent Redis-based job queue for Node.

Downloads

22

Readme

decent

npm version build status coverage status dependency status

decent is a decent Redis job queue for Node.js

Motivation

There are powerful job queue modules for node.js + redis out there, like kue and bull, to name a few. But powerful API comes at a price, they need complex data structure and redis scripts to achieve features such as delayed job, pause/resume and full text search. And since redis doesn't have traditional transaction, ie. no rollback when one of the command failed, and doesn't trigger error in node-redis driver, things can go south without developers noticing. Plus it's difficult to figure out what really happened due to non-intuitive redis data structure.

To us, the proper answer is to design around this problem, instead of adding more features, we want a job queue that's barebone, fully tested, easy to inspect, and doesn't hide errors from developers.

Features

  • Simple API with promise, works with your co/koa/whatever generator library.
  • Automatic job recovery that ease queue shutdown and restart.
  • Make use of native promise, and allow your favorite alternative.
  • Only dependency is the redis driver.

Install

npm install decent --save

Usage

TODO

API

decent(name, opts)

Create a queue with name and config redis client connection based on opts, returns a decent queue instance.

examples

var decent = require('decent');

var queue1 = decent('q1');
var queue2 = decent('q2', { 
	port: 6379
	, host: 'localhost'
	, connect_timeout: 5000 
});

opts

  • port: redis server port, default to 6379
  • host: redis server host, default to '127.0.0.1'
  • blockTimeout: how long a client should wait for next job (see redis document on blocking command, such as BLPOP), defaults to 60 seconds, 0 to block forever.
  • maxRetry: how many retries a job can have before being moved to failure queue, defaults to 3, 0 to disable retry.
  • and all redis client options.

queue.add(data, opts)

Create a job on queue using data as payload and allows job specific opts, returns a promise that resolve to the created job.

examples

queue.add({ a: 1 }).then(function(job) {
	console.log(job.data); // { a: 1 }
});

queue.add({ a: 1, b: 1 }, { retry: 1, timeout: 120 }).then(function(job) {
	console.log(job.data); // { a: 1, b: 1 }
	console.log(job.retry); // 1
	console.log(job.timeout); // 120
});

opts

  • retry: set initial retry counter, default to 0
  • timeout: set worker timeout in seconds, default to 60

job

  • id: job id
  • data: payload
  • retry: current retry count for this job
  • timeout: how many seconds a worker can run before it's terminated.
  • queue: which queue this job currently belongs to.

queue.worker(handler)

Register a handler function that process jobs, and start processing jobs in queue.

examples

queue.worker(function(job, done) {
	setTimeout(function() {
		console.log(job.data);
		done();
	}, 100);
});

done(err);

Must be called to signal the completion of job processing.

If called with an instance of Error, then decent will assume worker failed to process this job.

Fail jobs are moved back to work queue when they are below retry threshold, otherwise they are moved to failure queue.

queue.count(name)

Returns a promise that resolve to the queue length of specified queue, default to work queue.

examples

queue.count('work').then(function(count) {
	console.log(count); // pending job count
});

queue.count('run').then(function(count) {
	console.log(count); // running job count
});

queue.count('fail').then(function(count) {
	console.log(count); // failed job count
});

queue.get(id)

Returns a promise that resolve to the job itself.

examples

queue.get(1).then(function(job) {
	console.log(job.id); // 1
});

queue.remove(id, name)

Returns a promise that will resolve when job is removed from redis (both job data and job queue). Default queue is work.

Note: remove does not return the job, use get then remove instead.

examples

queue.remove(1, 'run').then(function() {
	// job has been removed from redis
});

queue.stop()

Instructs queue worker to terminate gracefully on next loop. See events on how to monitor queue.

examples

// ... setup queue and worker

queue.on('queue stop', function() {
	console.log('queue stopped gracefully');
});
queue.stop();

queue.restart()

Restarts the queue worker loop. See events on how to monitor queue.

examples

// ... setup queue and worker

queue.on('queue start', function() {
	console.log('queue restarted');
});
queue.restart();

Events

decent is an instance of EventEmitter, so you can use queue.on('event', func) as usual.

queue worker related

  • queue.emit('queue start'): queue loop has started.
  • queue.emit('queue work', job): queue worker begin to process a job.
  • queue.emit('queue ok', job): queue worker has processed a job.
  • queue.emit('queue error', err, job): queue worker has failed to processed a job and thrown err, will retry later.
  • queue.emit('queue failure', err, job): queue worker has failed to processed a job and thrown err, retry limit reached.
  • queue.emit('queue exit', err): queue loop has terminated due to unhandled err.
  • queue.emit('queue stop'): queue loop has stopped gracefully.

License

MIT