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

redis-streams-aggregator

v1.0.11

Published

Aggregate redis streams connections, powered by ioredis

Downloads

78

Readme

A connection collapser and toolkit built around Redis5's XADD and XREAD commands, powered by ioredis    

What? Why?

Redis 5 adds Streams, a powerful new data structure which simplifies the construction of real-time applications. The new XREAD command blocks a redis connection while awaiting new data, allows reading from multiple streams, and can be canceled with the new CLIENT UNBLOCK command. This package wraps XREAD and XADD such that new subscriptions automatically UNBLOCK the existing stream, add their new subscription (and handle offset tracking), and restart the stream. The end effect is that you'll need only two Redis connections open - one for reading and one for writing (including the UNBLOCKing).

With redis-streams-aggregator, you can just call .subscribe() and .add() and leave the stream management to us!

Install

yarn add redis-streams-aggregator

Use

const RedisStreamsAgg = require("redis-streams-aggregator");
const streams = new RedisStreams(); // options like: { host: ..., port: ... } etc

// Sign up for XREAD, get all messages to 'testId' in real-time
streams.subscribe("testId", messages => {
  console.log("I got messages!", { messages });
});

// Write data to a stream (very thin wrapper around XADD)
streams.add("testId", { value: "foobar" });

API Documentation

Messages

Messages events provide arrays of "Message" objects, which have the following properties:

const Message = {
  offset: string,
  key: value,
  key2: value2...
}

For example, consider the following:

// Server
streams.add("testChannel", { foo: "bar" });

streams.subscribe("testChannel", "$", messages => {
  // messages === [
  //  [ "1518951480106-0", { foo: 'bar' } ]
  // ]
});

Server

RedisStreamsAggregator(options)

Where "options" is an object with the following properties:

| Option | Required | Default | Description | | :------------ | :------: | :--------------: | ----------------------------------------- | | host | no | localhost | Redis host uri | | port | no | 6379 | Redis port | | serialize | no | JSON.stringify | A function for encoding published objects | | unserialize | no | JSON.parse | A function for decoding published objects |

const server = new RedisStreamsAggregator({
  host: "192.168.0.1",
  port: 6379
});

Server Events

  • ready - Connected to Redis
  • connect - A new socket has connected
  • error - An error has been encountered (connection to Redis failed, etc)