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

attrition

v0.0.6

Published

Simple queue/worker library for MongoDB.

Downloads

10

Readme

Attrition

Attrition is a simple queue system that uses a mongoDB collection to store jobs.

Attrition handles task-locking between processes so you can run many instances of a worker service, tasks are unlocked after a timeout (default 15 minutes).

Tasks whos worker function raise an error remain in the queue and are blocked, after which manual intervention is required. The objective here is that no tasks should ever be lost.

Why would I use this over a 'proper' *MQ service?

Because you might not want to add another SPOF to your deployment. For us, Mongo, while clustered is a critical failure point, if mongo is not accessible then no service is available. Adding an MQ system introduces another critical failure point that needs to be managed, MongoDB is quite capable of managing a queue of tasks.

TODOs

  • Write more unit tests
  • Implement healthCheck

Contrived Example:

Here is a simple queue example that uses a state flag to pass a task between workers.

var attrition = require("attrition");

var queue = mongoDB.collection('queue');

// Start polling the queue and match tasks with state == 'invoicing'
attrition.start(queue, {state : 'invoicing'}, sendInvoiceWorker);

// Start polling the queue and match tasks with state == 'shipping'
attrition.start(queue, {state : 'shipping'}, shippingWorker);

function sendInvoiceWorker(task, callback) {
    //Send an invoice logic..

    // Now update the task to set it's state to 'shipping' by passing some
    // updates and passing true to keep the task in the queue. 
        callback(err, true, {$set : {state : 'shipping'}}); // pass true to keep the task in the queue. 
    });
}

function shippingWorker(task, callback) {
    // Initiate shipping logic..

    // finished with the task, pass false and it will be removed from the queue. 
    callback(err, false); 
}

//send a task to the queue
attrition.queue(queue, {state : 'invoicing', data : { shippingAddress : {...}}}, callback);