ØMQ bindings for node.js.
Ensure you're building zmq from a conservative location on disk, one without
unusual characters or spaces, for example somewhere like:
Installing the ZeroMQ library is optional and not required on Windows. We
npm install and node executable commands from a
github for windows shell or similar environment.
pkg-config and the ZeroMQ library.
This module is compatible with ZeroMQ versions 2, 3 and 4. The installation
process varies by platform, but headers are mandatory. Most Linux distributions
provide these headers with
-devel packages like
zeromq3-devel. Homebrew for OS X provides versions 4 and 3 with packages
zeromq3, respectively. A
Chris Lea PPA
is available for Debian-like users who want a version newer than currently
provided by their distribution. Windows is supported but not actively
Note: For zap support with versions >=4 you need to have libzmq built and linked against libsodium. Check the Travis configuration for a list of what is tested and therefore known to work.
$ npm install zmq
// producer.jsvar zmq =sock = zmq;sock;console;;
// worker.jsvar zmq =sock = zmq;sock;console;sock;
// pubber.jsvar zmq =sock = zmq;sock;console;;
// subber.jsvar zmq =sock = zmq;sock;sock;console;sock;
You can get socket state changes events by calling to the
The supported events are (see ZMQ docs for full description):
All events get 2 arguments:
fd- The file descriptor of the underlying socket (if available)
endpoint- The underlying socket endpoint
monitor_error event will be raised when there was an error in the monitoring process, after this event no more
monitoring events will be sent, you can try and call
monitor again to restart the monitoring process.
Will create an inproc PAIR socket where zmq will publish socket state changes events, the events from this socket will
be read every
interval (defaults to 10ms).
By default only 1 message will be read every interval, this can be configured by using the
where passing 0 will read all available messages per interval.
Stop the monitoring process
// Create a socketvar zmq = ;socket = zmq;// Register to monitoring eventssocket;socket;socket;socket;socket;socket;socket;socket;socket;socket;// Handle monitor errorsocket;// Call monitor, check for events every 500ms and get all available events.console;socket;socket;;
You may temporarily disable polling on a specific ZMQ socket and let the node.js
process to terminate without closing sockets explicitly by removing their event loop
references. Newly created sockets are already
Detach the socket from the main event loop of the node.js runtime. Calling this on already detached sockets is a no-op.
Attach the socket to the main event loop. Calling this on already attached sockets is a no-op.
var zmq = ;socket = zmq;socket;socket;socket
$ git clone https://github.com/JustinTulloss/zeromq.node.git zmq && cd zmq$ npm i
# on unix:$ make# building on windows:> npm i
# on unix:$ make test# testing on windows:> npm t
Benchmarks are available in the
perf directory, and have been implemented
according to the zmq documentation:
How to run performance tests
In the following examples, the arguments are respectively:
You can run a latency benchmark by running these two commands in two separate shells:
node ./local_lat.js tcp://127.0.0.1:5555 1 100000
node ./remote_lat.js tcp://127.0.0.1:5555 1 100000
And you can run throughput tests by running these two commands in two separate shells:
node ./local_thr.js tcp://127.0.0.1:5555 1 100000
node ./remote_thr.js tcp://127.0.0.1:5555 1 100000
make perf will run the commands listed above.