A ZeroMQ based microservices framework for NodeJS.

The goal is to offer a reliable and extensible service-oriented request-reply inspired by Majordomo Protocol (MDP) v0.2 and Titanic Service Protocol.

• Worker : receives requests, does something and replies. A worker offers a service, should be a functionality as atomic as possible
• Client : creates, pushes requests and waits for results (if needed). A request always includes a service and a payload/data for the Worker
• Broker : handles requests queueing and routing

• Broker examples/broker.js
• Worker examples/echo/echo_worker.js
• Client examples/echo/echo_client.js

PIGATO-EXAMPLES : a collection of multi-purpose useful examples.

Simply starts up a broker.

var Broker = require('./../index').Broker;

var broker = new Broker("tcp://*:55555");
broker.start(function(){});

Worker receives "request" events that contain 2 arguments:

• data - value sent by a client for this request.
• reply - extended writable stream to send data to the client.

reply writable stream exposes also following methods and attributes:

• write() - sends partial data to the client (triggers partial callback). It is used internally to implement writable streams.
• end() - sends last data to the client (triggers final callback) and completes/closes current request. Use this method for single-reply requests.
• reject() - rejects a request.
• heartbeat() - forces sending heartbeat to the broker and client
• active() - returns (boolean) the status of the request. A request becomes inactive when the worker disconnects from the broker or it is discarded by the client or the client disconnects from the broker. This is useful for long running tasks and Worker can monitor whether or not continue processing a request.
• ended - tells (boolean) if the request has been ended.

var worker = new pigato.Worker('tcp://localhost:12345', 'MyService');

worker.on('request', function(data, reply) {
  fs.createReadStream(data).pipe(reply);
});

// or
worker.on('request', function(data, reply) {
  for (var i = 0; i < 1000; i++) {
    res.write('PARTIAL DATA ' + i);
  }
  res.end('FINAL DATA');
});

Worker may also specify whether the reply should be cached and the cache timeout in milliseconds

worker.on('request', function(data, reply) {
  res.opts.cache = 1000; // cache reply for 1 second
  res.end('FINAL DATA');
});

Take note: due to the framing protocol of zmq only the data supplied to response.end(data) will be given to the client's final callback.

Clients may make requests using Client.request(...) method.

• serviceName - name of the service we wish to connect to
• data - data to give to the service (string/object/buffer)
• opts - options object for the request

var client = new pigato.Worker('tcp://localhost:12345');

client.request('my-service', 'foo', { timeout: 120000 }).pipe(process.stdout);

// or
client.request('my-service', { foo: 'bar' }, { timeout: 120000 })
.on('data', function(data) {
  console.log("DATA", data);	
})
.on('end', function() {
  console.log("END");	  
});

Clients may also make request with partial and final callbacks instead of using streams.

• serviceName
• data
• partialCallback(err, data) - called whenever the request does not end but emits data
• finalCallback(err, data) - called when the request will emit no more data
• opts

client.request('my-service', 'foo', function (err, data) {
  // frames sent prior to final frame
  console.log('PARTIAL', data);
}, function (err, data) {
  // this is the final frame sent
  console.log('FINAL', data);
}, { timeout: 30000 });

• timeout : default 60000 (60 seconds). Set -1 to disable (time unlimited request)

• when using a inproc socket the broker must become active before any queued messages.

• Reliable request / reply protocol
• Scalability
• Multi-Worker : infinite services and infinite workers for each service
• Multi-Client : infinite clients
• Multi-Broker : infinite brokers to avoid bottlenecks and improve network reliability

• Compatibility with MDP protocol v0.2 .
• Support for partial replies.
• Client multi-request support.
• Client heartbeating for long running requests. Allows Workers to dected whenever Clients disconnect or lose interest in some request. This feature is very useful to stop long-running partial requests (i.e data streaming).

• Worker <-> Broker heartbeating.
• Broker MAY track Worker/Client/Request relation.
• Client MAY send heartbeat for active request. If the request is being processed by Worker, Broker forwards heartbeat to Worker.
• Worker MAY decide to stop an inactive Request (tracks liveness for Request).
• Client MAY assign a timeout to a Request.
• Worker SHALL NOT send more W_REPLY (for a Request) after sending first W_REPLY message.
• Broker SHALL force disconnect Broker if any error occurs.

• Add authentication support through zmq-zap ZeroMQ ZAP to trust Clients and Workers.
• Support Titanic Service Protocol for peristent requests.

• Fincluster - cloud financial platform : fincluster / @fincluster
• My personal blog : ardoino.com / @paoloardoino

• bmeck

Based on https://github.com/nuh-temp/zmq-mdp2 project