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

server-events

v1.0.2

Published

Cross-server eventing

Downloads

3

Readme

server-events

An asynchronous cross-server eventing. Uses Redis Pub/Sub messaging system for cross-server communication.

Example

Say we have N servers servicing an API for an app and a worker server running some heavy loads. All the servers are connected to a Redis cluster. An action by the app triggers a worker job that produces a result in an unknown time. A result that the app is interested in. ServerEvents allows an API endpoint to respond with the result just as it becomes available. Worker can send a response to an endpoint instance on a particular server right after it has finished running a job. If worker fails to deliver results in time, the event will time out and the API endpoint can respond with a controlled message.

Usage

Initialization

Intialize a ServerEvents instance by providing Redis server options. Optionally you can subscribe to listen 'ready' and 'error' events.

const ServerEvents = require('server-events');

const randomEvents = new ServerEvents({
    host: 'localhost',
    port: 6379,
    db: 0
});

randomEvents.onready(function() {
    console.log('randomEvents are ready');
});

randomEvents.onerror(function(store, error) {
    // store can be either 'outputStore' or 'inputStore'
    console.log(store, error);
});

Triggering events

Events are referenced by name and id. The name specifies context while id can be used to reference a certain object (i.e. database table index).

    randomEvents.emit('not so random', 12);

Additional arguments passed to the emitter will be passed on to the listener.

    randomEvents.emit('pi event', 314, 'arg1', 1, {type: 'object'});

Waiting for events

Events returned as promises. Provide a thenable if you wish to get the results as an array.

    randomEvents.on('pi event', 314).then(function(result) {
        // result ~ ['arg1', 1, {type: 'object'}]
    });

Or spreadable to receive them naturally.

    randomEvents.on('pi event', 314).spread(function(a, b, c) {
        // a ~ 'arg1', b ~ 1, c ~ {type: 'object'}
    });

Event timeout will result in an error.

    randomEvents.on('wont', 'happen').catch(function(error) {
        // event has timed out
    });

Custom timeout can be passed.

    randomEvents.on('ev', 101, 5000).catch(function(a) {
        // event will timeout after 5000 ms unless result is returned
    });

Options

The default timeout for all ServerEvents instances is 10000 ms. This can be overriden for each instance:

    randomEvents.timeout = 1000; // 1 second

Test

npm test