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 🙏

© 2026 – Pkg Stats / Ryan Hefner

microservices-layer

v0.1.12

Published

A wrapper for microservices strategies, with Pigato (ZeroMQ)

Readme

Microservices Layer

EARLY ALPHA, DON'T USE IT IN PRODUCTION!

A wrapper for microservices strategies, based on Pigato (ZeroMQ) with an optional network abstraction for Docker Links.

Also provides Pub/Sub functionalities .

Install

npm install --save microservices-layer

How to use

Client

Localhost


var port = 1234;
var host = 'localhost';

var MsLayer = require('microservices-layer');
MicroServices = new MsLayer.Client(port, host);

MicroServices.request(
  // the service identifier string. DON'T use hifens or underscores in the name.
  'someservice',
  // the json payload
  {
    some: 'payload',
    any: 'data'
  },
  // callback
  function(err, response){
    // do something
  }
);

Between Docker Containers

Since 1.0.6 you can abstract your network between Docker containers using Docker Links. Just use the same string for your service name and your service's Docker container/link (In the service).


var port = 1234;

var MsLayer = require('microservices-layer');
MicroServices = new MsLayer.Client(port, null, {docker:true});

MicroServices.request(
  // the service identifier string. DON'T use hifens or underscores in the name.
  'someservice',
  // the json payload
  {
    some: 'payload',
    any: 'data'
  },
  // callback
  function(err, response){
    // do something
  }
);

Client is lazy, it means that the tcp connection with zmq will be only open the first time the service is called and, as the connection is based on the service name, you don't need any additional configuration besides the Docker Links. Just request the service by its name, enywhere in your code.

Service

The service will not change its configuration, it will be the same for localhost or Docker environments. Just use the right service name.


var MsLayer = require('microservices-layer');

var serviceName = 'someservice'; // the service identifier string. DON'T use hifens or underscores in the name.
var serviceConfigs = {
  port: 1234
};
var serviceGateway = function(params, reply){

  // some logic maybe...
  switch(params.cmd){

    // call some internal functions
    case "create" : createSomething(params, function(data){ reply.end(data); }); break;
    case "read"   : readSomething(params, function(data){ reply.end(data); }); break;
    case "update" : updateSomething(params, function(data){ reply.end(data); }); break;
    case "delete" : deleteSomething(params, function(data){ reply.end(data); }); break;

    // invalid command
    default:
      reply.end({
        sta: 0,
        msg: 'invalid:cmd'
      });
  }
};

var service = new MsLayer.Service(serviceName, serviceGateway, serviceConfigs);

Pub/Sub

Since 0.1.2 you can use Pub/Sub directly with this module and with a very simple syntax.

Publisher


var MsLayer = require('microservices-layer');

var Publisher = new MsLayer.Pub(3002);

// then, somewhere in your code...
Publisher.publish('SomeEvent', { some:'value', other: 'value' });

Subscriber


var MsLayer = require('microservices-layer');

Subscriber = new MsLayer.Sub(3002);

// subscription is automatic, just set your callback
Subscriber.on('someEvent', function(data){
  // do something
});