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

ges-competing-consumer

v0.0.2

Published

A Node.js utility for consuming (Get) Event Store Competing Consumer subscriptions using Event Store's HTTP API.

Downloads

16

Readme

node-ges-competing-consumer

A Node.js utility for consuming (Get) Event Store Competing Consumer subscriptions using Event Store's HTTP API.

Installation

Available on npm:

npm install ges-competing-consumer

Documentation

let consumer = new CompetingConsumer(stream, group, handler, options)

The CompetingConsumer constructor takes the following arguments:

  • stream: The stream to consume.
  • group: The name of the configured subscription group.
  • handler: The function to invoke with each incoming event. The handler function must take a single event argument, which is the raw event as received from Event Store. It must return a promise, which resolves when the event has been processed, or rejects in case of an error. When the promise resolves, the event will be ack'ed with Event Store, and when it rejects the event will be nack'ed with Event Store. See Usage example below.
  • options: A hash of options:
    • eventStoreUrl: The Event Store URL with protocol, domain and port. Example: http://eventstore.example.com:2113. If not set, we will default to using process.env.EVENT_STORE_URL. And if neither of those are set an exception will be thrown at runtime.
    • concurrency: Maximum number of events to handle concurrently. Defaults to 1, meaning that the consumer won't pull any events from the subscription until the current event has been handled and ack'ed.
    • onEvent: Callback for logging purposes. Invoked when an even is received. Called with the event as its single argument. Defaults to do nothing.
    • onAck: Callback for logging purposes. Invoked when an event is acked. Called with the event as its single argument. Defaults to do nothing.
    • onNack: Callback for logging purposes. Invoked when an even is nacked. Called with the event as its single argument. Defaults to do nothing.
    • onError: Callback for logging purposes. Invoked when an error occurs (fx a bad status code from Event Store, or a handler that rejects) is received with the event as its single argument. Defaults to console.error() log the error stack.

Note: You must create the Competing Consumer subscription in Event Store first manually.

consumer.start()

Will tell the consumer to start pulling from the subscription. Nothing happens until you call this function.

consumer.stop()

Tells the consumer to stop pulling. Returns a promise which resolves after all already active events have been handled and ack'ed. After the promise resolves it's safe to stop the Node process.

Usage example

import CompetingConsumer from 'ges-competing-consumer'

function handler(event) {
    //`event` is the raw event from Event Store
    //You can get the event data like this:
    let data = JSON.parse(event.data)

    //The consumer will wait until the `handler` function resolves before ack'ing to Event Store
    return doImportantWork(data) //returns a promise
}

let consumer = new CompetingConsumer('MyStream', 'my-group', handler, {
    eventStoreUrl: 'http://eventstore.example.com:2113',
    concurrency: 5
})

//Start pulling events
consumer.start()

//Stop after 10 seconds
setTimeout(function() {
    consumer.stop()
        .then(() => {
            console.log('Done for today!')
            process.exit()
        })
}, 10 * 1000)