Netcluster NPM

netcluster

Network based cluster for Node.js

Last updated at: 04-JAN-2016 9:43 GMT-2

This is the first offical version, and some changes were required in the lib interface - I am sorry for the extra effort required to fix, but I undersand is minimal - mainly related to the way objects should be created.

IMPORTANT:

From v 1.0.0 onward, all events are locally routed (in memory) as well.
Events are now managed using xtraemitter so Regex can be used to bind listeners. Please refer to its doc on: (https://github.com/paulosimao/xtraemitter),
For windows users: You can now install cluster server as a service - please see below.
Unix users, you have all you need + cron or pm2 to have phun, right?

Default cluster lib works great as long as you´re in the same machine. Once you need to scale along multiple machines things start to get complicated.

Also, there are situations where your processed to be stand alone, but share computing skills.

This was the motivation to develop this lib.

In a short:

It exchanges messages locally through memory and pipes, each pipe is mapped in a channel. Roles for propagating messages among channels can be defined. It also exchange messages through UDP and routing can also be defined.

Conclusion: You can emit and listen to events in different processes and machines, but it also works within the same process, so your code can scalate with fewer changes.

Later it can incorporate different, multiple protocols.

For now, it works on top of UDP and Unix Socket / Windows Pipes and without any cryptography.

How it works (The BIG Landscape):

You need to create a local server to coordinate unix sockets (see ncserver_ in case you wont create your own.)
You need to connect to this server somehow (please see below)
You may send and receive messages
In case you want to exchange messages w different boxes, you need to enable UDP connection on the local server process.

How to install:

npm install -g netcluster

In case you want to use provided server, the command ncserver will be available. If no parameters are provided, it will use the config.json in the same folder ncserver is, otherwise, provide the FULL PATH to the config file you want to use.

ncserver_posix - Command to start provided server on *nix
ncserver_win - Command to start provided server on windows
ncclient_posix - Command to start provided control client on *nix
ncclient_win - Command to start provided control client on windows

Both accept Full Qualified Path to config file(see below) as the only parameter.

Client Commands:

Once you run ncclient, it will start a REPL, allowing you to issue the following functions:

showconfig() : Dumps the active configuration on the server
reloaconfig (path) : Reloads the config. Mandatory parameter is the full path of file. Remember that \ needs to be escaped (double them).
showchannel (channame) : Shows you the uuid of clients connected to that channel.
showclient (chan,uuid) : Shows info about that client (Broken at the moment).

Please note these are functions available in REPL context, not REPL commands (the ones starting w/ .)

Snippets:

Config (control channel must exist ALWAYS):

{
  //UDP Multicast addr
  "addr": "224.0.0.0",
  //UDP Multicast port
  "port": 4454,
  //In case you want to dump whatever comes over the socket to console
  "dumpnet": true,
  //Tells wether this instance will connect to the network or not
  "connecttonet": true,
  //Tells whether you want to start control channel agent
  "startcontrol": true,
  //This are the channels - each is an independent local socket
  "channels": {
    //channel name
    "control": {
       //Tells to wich channels msgs should be propagated. If false none,
       //if string, should be a Regex pointing to associated names.
      "propagatetochannels": false,
      //Tells if msgs should go to network also
      "propagatetonet": false,
      //Tell if msgs on this channel should be dumped to console
      "dumptoconsole": false
    },
    "A": {
      "propagatetochannels": ".*",
      "propagatetonet": false,
      "dumptoconsole": false
    },
    "B": {
      "propagatetochannels": ".*",
      "propagatetonet": false,
      "dumptoconsole": false
    }
  }
}

Local Server (in case you want to embed):

var fs = require('fs');
var Server = require('netcluster').NCServer;
var server = new Server();
var confstr = fs.readFileSync(process.argv[2] ? process.argv[2] : 'config.json');
var conf = JSON.parse(confstr);
server.config = conf;
server.start();

Receiver:

//Requires
var Agent = require('netcluster').NCAgent;
//Create client
var agent = new Agent();
//connect to channel
agent.connect('B', function () {
    //assigns listener to on msg
    agent.on('log', function (msg) {
    console.log('A called:' + JSON.stringify(msg));
    agent.disconnect();
    });
});

Sender:

//Requires
var Agent = require('netcluster').NCAgent;
//Create client
var agent = new Agent();

//Bind to local server
agent.connect('A', function () {
    function loop() {

        //Emit event
        agent.emit('log', 'TESTE');
        setTimeout(loop, 1000);
    }

    loop();

});
});

Relevant Interface:

Local Server:

start: function () : Initiate local server and binds it to the associated path.

Client:

connect: function (channel, cb) : Connects client to local addr
disconnect: function () : Disconnects
emit: function (event, data): Send event and data associated to in
on: function (event, cb) : Function triggered once message is received. cb should have one parameter to receive the message itself.
once: function (event, cb): Same as above,but triggered only once and not at every message
removeListener(event, cb): Removes a listener.

For these, please refer to node events API (https://nodejs.org/api/events.html)

Install/Uninstall Server as a service in windows:

Create a key under HKLM, named \Software\Netcluster
Create a new String value called conf
Put the FULL PATH to the conf file as the value of conf.

RUN ALL COMMANDS AS ADMINISTRATOR (Right click on cmd shortcut, run as administrator)

Purposely repeated 3 times ;^)

Install Open cmd and go to the root where netcluster was installed (I suggest using -g with its installation). In case you installed it as global, it should be on: C:\Users\<USER>\AppData\Roaming\npm\node_modules\netcluster where is the username of the person who installed it (and is supposed to run the service).

run the command: node bin\win_install_svc.js

Unistall Same as above, but command at the end is: node bin\win_uninstall_svc.js

TODO:

A lot of testing is required at the moment. Pleas provide feedback, and if possible register bugs into GITHUB (https://github.com/paulosimao/netcluster)