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

retask

v0.2.0

Published

Redis-based dispatcher to parallel pipelines.

Downloads

7

Readme

retask

Redis-based dispatcher to parallel task pipelines.

Use case

We require a persistent pubsub setup via Redis lists, e.g. to support parallel task queues.

Some "publisher" pushes a message onto a Redis list. This service pops each message, and pushes it onto multiple target lists, one for each subscriber. Each subscriber pops messages from their own dedicated Redis list.

This replaces a previously implemented solution for the same use case: https://github.com/evanx/mpush-redis

Config

See config.js

module.exports = {
    description: 'Redis-based dispatcher to parallel pipelines.',
    required: {
        host: {
            description: 'the Redis host',
            default: 'localhost'
        },
        port: {
            description: 'the Redis port',
            default: 6379
        },
        popTimeout: {
            description: 'the timeout for brpoplpush',
            unit: 'seconds',
            default: 10
        },
        inq: {
            description: 'the source queue',
        },
        busyq: {
            description: 'the pending queue for brpoplpush',
        },
        outqs: {
            description: 'the target queues',
            elementType: 'string'
        }        
    }
}

Docker

You can build as follows:

docker build -t retask https://github.com/evanx/retask.git

See test/demo.sh https://github.com/evanx/retask/blob/master/test/demo.sh

Builds:

  • isolated network retask-network
  • isolated Redis instance named retask-redis
  • this utility evanx/retask

Isolated test network

First we create the isolated network:

docker network create -d bridge retask-network

Disposable Redis instance

Then the Redis container on that network:

redisContainer=`docker run --network=retask-network \
    --name $redisName -d redis`
redisHost=`docker inspect $redisContainer |
    grep '"IPAddress":' | tail -1 | sed 's/.*"\([0-9\.]*\)",/\1/'`

where we parse its IP number into redisHost

Setup test data

We push an item to the input queue:

redis-cli -h $redisHost lpush in:q '46664'

Build and run

We build a container image for this service:

docker build -t retask https://github.com/evanx/retask.git

We interactively run the service on our test Redis container:

docker run --name retask-instance --rm -i \
  --network=retask-network \
  -e host=$redisHost \
  -e inq=in:q \
  -e busyq=busy:q \
  -e outqs=out1:q,out2:q \
  retask

Verify results

evan@dijkstra:~/retask$ sh test/demo.sh
...
+ redis-cli -h $redisHost lrange out1:q 0 -1
1) 46664
+ redis-cli -h $redisHost lrange out2:q 0 -1
1) 46664

Teardown

docker rm -f retask-redis
docker network rm retask-network

Implementation

See app/main.js

while (true) {
    const item = await client.brpoplpushAsync(config.inq, config.busyq, config.popTimeout);
    logger.debug('pop', config.inq, config.busyq, config.popTimeout, item);
    if (!item) {
        break;
    }
    if (item === 'exit') {
        await client.lrem(config.busyq, 1, item);
        break;
    }
    await multiExecAsync(client, multi => {
        config.outqs.forEach(outq => multi.lpush(outq, item));
        multi.lrem(config.busyq, 1, item);
    });
}

Appication archetype

Incidently app/index.js uses the redis-app-rpf application archetype.

require('redis-app-rpf')(require('./spec'), require('./main'));

where we extract the config from process.env according to the spec and invoke our main function.

See https://github.com/evanx/redis-app-rpf.

This provides lifecycle boilerplate to reuse across similar applications.