hisco / process-cluster

Have a forever running nodejs cluster (not only nodejs core cluster module)

Process cluster

process-cluster will asist you in creating any child process cluster, it uses forever-process to makes sure that cluster will run forever.

Features

• Fork a child process
• Spawn any process
• Fork a chile process with node cluster capabilities
• To any size of cluster
• Cluster will run forever, we use forever-process to make sure it does.

Simple usage

Creating a cluster of Node cluster module. Notice, the with this multiple nodejs process will be able to "share"(over IPC) the same port when receiving any net requst such as http.

const {ProcessCluster} = require('process-cluster');
const cluster = require('cluster');
const processCluster = new ProcessCluster({
    size : 3,
    fork(){
        cluster.setupMaster({
                exec : `${prcessPath}`,
                args : [ 
                    ...process.argv.slice(2)
                ]
            });
        return cluster.fork();
    }
});
processCluster.on('childProcess' , (childProcess)=>{
    console.log('You can do any operation on `childProcess`');
});
processCluster.on('childProcessRemoved' , (childProcess)=>{
    console.log('Removed');
});
processCluster.start();

Creating a cluster of Node process with IPC communication without 'port' sharing.

const {ProcessCluster} = require('process-cluster');
const {fork} = require('child_process');
const processCluster = new ProcessCluster({
    size : 3,
    fork(){
        return fork(`${prcessPath}`);
    }
});
processCluster.on('childProcess' , (childProcess)=>{
    console.log('You can do any operation on `childProcess`');
});
processCluster.on('childProcessRemoved' , (childProcess)=>{
    console.log('Removed');
});
processCluster.start();

API

Well, the API is quite simple. You can see this TypeScript declaration.

declare module ProcessCluster {
	export class ProcessCluster extends EventEmitter{
		constructor(options : {
            size : number,
            fork : ()=>ChildProcess
        });
		public createForkedChild():void;
		public removeForkedChild(child? : any):void;
		public forkToDetination():void;
		public increaseBy(size : number):void;
		public decreaseBy(size : number):void;
		public stop():void;
		public start():void;
	}
}

License

MIT

process-cluster's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.