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

hemera-nsq

v4.0.0

Published

This is a plugin to use NSQ with Hemera

Downloads

14

Readme

Hemera-nsq package

npm styled with prettier

This is a plugin to use NSQ with Hemera.

NSQ promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. It is complementary to the primary NATS transport system.

The client use JSON to transfer data.

Start NSQ with Docker

Steps

How does it work with NATS and Hemera

We use a seperate topic for each NSQ Topic/Channels because with that you can listen in every hemera service for events. Every message will be forwarded to the NATS subscriber. As you can see NSQ give you new possibilities how to distribute your data but without lossing the benefits of nats-hemera with regard to load balancing and service-discovery.

Install

npm i hemera-nsq --save

Example

hemera.use(require('hemera-nsq'), {
  nsqReader: {
    lookupdHTTPAddresses: [
      'http://localhost:4161'
    ]
  },
  nsqWriter: {
    host: 'localhost',
    port: 4150
  }
})

hemera.ready(() => {
  // create subscriber which listen on NSQ events
  // can be subcribed in any hemera service
  hemera.add({
    topic: 'nsq.newsletter.germany',
    cmd: 'subscribe'
  }, function (req, reply) {
    this.log.info(req, 'Data')

    // ACK Message, if you pass an error the message is reququed
    reply(/* new Error('test') */)
  })

  // create NSQ subscriber
  hemera.act({
    topic: 'nsq',
    cmd: 'subscribe',
    subject: 'newsletter',
    channel: 'germany'
  }, function (err) {
    if (err) {
      this.log.error(err)
      return
    }

    this.log.info('Subscribed ACK')
  })

  // Send a message to NSQ
  hemera.act({
    topic: 'nsq',
    cmd: 'publish',
    subject: 'newsletter',
    data: {
      to: 'klaus',
      text: 'You got a gift!'
    }
  }, function (err) {
    if (err) {
      this.log.error(err)
      return
    }

    this.log.info('Publish ACK')
  })
})

Requirements

  • node >=6.0.0 - Due to the rewrite of the nsqjs module only Node >= 6 is supported.

Interface


publish

The pattern is:

  • topic: is the service name to publish to nsq
  • cmd: is the command to execute publish
  • subject: the name of the NSQ topic string
  • data: the data to transfer object

Example:

hemera.act({
  topic: 'nsq',
  cmd: 'publish',
  subject: 'newsletter',
  data: {
    to: 'klaus',
    text: 'You got a gift!'
  }
}, ...)

Create subscriber

The pattern is:

  • topic: is the service name to publish to nsq
  • cmd: is the command to execute subscribe
  • subject: the name of the NSQ topic string
  • channel: the name of the NSQ channel string

Example:

hemera.act({
  topic: 'nsq',
  cmd: 'subscribe',
  subject: 'newsletter',
  channel: 'germany'
}, ...)

Consume events

The pattern is:

  • topic: is a combination of the subject and channel name nsq.<subject>.<channel>
  • cmd: is the command to execute subscribe

Example:

hemera.add({
  topic: 'nsq.newsletter.germany',
  cmd: 'subscribe'
}, ...)