At the moment, I am using EventEmitter2 as a message bus inside my application, and I really like it.
Anyway, now I need a message bus which does not only work in-process, but also inter-process. My ideal candidate would …
What I do not need:
Any ideas or hints?
PS: It is fine if you can recommend an available product, but it is also fine if you can point me into a direction of how to do the server-less thing by myself.
Node. js uses events module to create and handle custom events. The EventEmitter class can be used to create and handle custom events module.
a nodejs module for local and remote Inter Process Communication with full support for Linux, Mac and Windows. It also supports all forms of socket communication from low level unix and windows sockets to UDP and secure TLS and TCP sockets. A great solution for complex multiprocess Neural Networking in Node.JS.
libuv: libuv is a C library originally written for Node. js to abstract non-blocking I/O operations. Event-driven asynchronous I/O model is integrated. It allows the CPU and other resources to be used simultaneously while still performing I/O operations, thereby resulting in efficient use of resources and network.
The EventEmitter is a module that facilitates communication/interaction between objects in Node. EventEmitter is at the core of Node asynchronous event-driven architecture. Many of Node's built-in modules inherit from EventEmitter including prominent frameworks like Express.
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
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
Good old TCP.
node-to-node socket.io
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).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With