Here are your options as I see them.
process.fork/send. If both processes are node, node core provides a simple, event-driven IPC mechanism via this API. It pairs with
process.fork
so if your processes are a node-based master and several node-based worker/support subprocesses,process.send
might be a viable choice. http://nodejs.org/docs/latest/api/all.html#all_child_process_fork_modulepath_args_options- event-based, but not EventEmitter2 drop-in
- bi-directional
- efficient
- uses only OS resources
- in-memory
- javascript
Use node core's TCP networking to connect via a unix domain socket. http://nodejs.org/docs/latest/api/all.html#all_net_connect_options_connectionlistener
- still event based but raw data stream as opposed to high-level messages
- bi-directional
- in-memory
- javascript
Good old TCP.
- still event based but raw data stream as opposed to high-level messages
- bi-directional
- in-memory
- javascript
node-to-node socket.io
- event based, but not EventEmitter2 drop-in
- bi-directional
- in-memory
- javascript
In all cases you get bi-directional communication once connected, but there is always the concept of the first peer (server in TCP or socket.io, parent process in process.fork) and second peer (client in TCP or socket.io, child process in process.fork).