node package manager
Share your code. npm Orgs help your team discover, share, and reuse code. Create a free org ¬Ľ


Quick Bus ūüöĆ

A tiny event bus with AMQP and Postal.js-like functionality meant to be used on the client-side.


Proudly built by:

What is it?

This is a simple event bus that replicates the basics of Postal.js in about 80 lines of code (minified to 773 bytes)

It doesn't use lists of regex like Postal does but uses a directed graph instead, which is much faster.

It adds a history for automatic metrics collection, which brings the line count to about 150 lines of code (minified to 1258 bytes)

It has no dependencies.

How to use

Use the emit and on methods, just like a regular event emitter.

var channel = new Bus();
channel.on('metrics.#', function (msg) {
channel.emit('', 'hello world');

In imitation of Postal.js, use the returned function to stop the events.

var off = channel.on('page.load.justOnce', function (msg) {

Also in imitation of Postal.js, use the second parameter to get the topic that triggered the event.

var off = channel.on('*.filled', function (msg, meta) {
  console.log(meta.topic + 'just happened');

If you like the pub/sub model better, we've aliased subscribe and publish as well:

var channel = new Bus();
channel.subscribe('metrics.#', function (msg) {
channel.publish('', 'hello world');

And of course to unsubscribe, use the returned function:

var unsubscribe = channel.subscribe('#', function (msg) {
  console.log(, msg);
for (var i = 0; i < 10; i++) {
  channel.publish('welcome.' + i, 'hello world!');

How it works

A Bus builds a directed graph of subscriptions. As event topics are published, the graph discovers all the subscribers to notify and then caches the results for faster message publishing in the future. When a new subscriber is added, the graph is modified and the subscriber cache is reset.

Wildcard subscriptions

Supports same wildcards as Postal.js, such as:

Zero or more words using #

channel.subscribe('#.changed', function (msg) {
  // ...
channel.emit('what.has.changed', event);
channel.subscribe('metrics.#.changed', function (msg) {
  // ...
channel.emit('metrics.something.important.has.changed', event);

Single word using *

channel.subscribe('ads.slot.*.filled', function (msg) {
  // ...
channel.emit('', {data, msg});


We keep a history of the events that have been emitted. They can be queried with the history method:

var channel = new Bus();
channel.emit('', {data, msg});
channel.emit('ads.slot.side-rail.filled', {thing, stuff});
channel.emit('ads.slot.instream-banner-0.filled', {a, b});
channel.emit('metrics.component.absdf2324.render.start', {etc, ie});
channel.emit('metrics.component.absdf2324.render.end', {etc, ie});
// gets the ad slots that were filled
var history = channel.history('ads.slot.*.filled');
// gets history of components rendering
var history = channel.history('metrics.component.*.render.*');

The format is an array of arrays. For example:

  ["", 1515714470550],
  ["ads.slot.side-rail.filled", 1515714470559],
  ["ads.slot.instream-banner-0.filled", 1515714500268],
  ["metrics.component.absdf2324.render.start", 1515714782584],
  ["metrics.component.absdf2324.render.end", 1515714790507],

Only the topic and the timestamp of each event is stored. We don't store the message/payload in the history to prevent potential memory leaks and scoping issues.

These events are stored in a ring buffer, so old events will be dropped from the history once it reaches a certain size. The history size is current set to a maximum of 9999 events.

Note that this feature is designed for metrics, and often the information that people are interested in for metrics can be included as part of the topic. For example, if you have a subscriber of on('components.*.render.start'), then you can have an infinite number of component ids such as emit('components.abcdef.render.start') and emit('components.someRandomId.render.start') without any additional complexity or performance penalty to the event bus. If you're trying to access more information that can't be included as part of the topic, then you should make a subscriber and log that information.

Look at our Examples Page for some common code patterns with event buses.

To Do

  • Determine if the "meta" field from Postal.js should be included, or if that's just weight that the Promise API hates
  • Should we expose timing information or the ids of messages?
  • Would an async mechanism that would collect, buffer, or throttle messages be useful? Would an event queue be used?
  • Are there other features of Postal that we actually use?

Future / Related architecture

  • Create helper library specialized in producing events from React
  • Create library to link into Browser events (Boomerang)
  • Create library to collect events and forward them to servers such as Sparrow, GA or BoomCatch.

Related Documents

Related Topics