ZeroMQ Installation, Core Messaging Patterns, and Usage Guide

ZeroMQ (ØMQ) is a high‑performance asynchronous messaging library; its official API documentation is available at http://api.zeromq.org/ and additional introductions can be found online.

Installation – Download the source, extract it, and compile:

tar zxf zeromq-4.0.3.tar.gz

cd zeromq-4.0.3

./configure

make

make install

The official website is http://zeromq.org/ .

Advantages – ZeroMQ wraps basic socket functionality, provides automatic reconnection, message framing, and defines clear interaction modes; unlike traditional sockets, it supports N‑to‑M communication patterns.

Core Messaging Patterns

1. PUB‑SUB – Multiple subscribers receive broadcasts from a publisher. Note that messages sent before a subscriber connects are lost.

2. REQ‑REP – Strict request‑reply sequence: a client sends a request (ZMQ_REQ) and waits for a reply from the server (ZMQ_REP). Only one reply per request is allowed.

3. PUSH‑PULL – One‑way pipeline where PUSH sockets send data that is received by exactly one PULL socket.

Important Notes

Setting socket.setsockopt_string(zmq.SUBSCRIBE, "") subscribes to all messages.

It is recommended that PUB sockets bind and SUB sockets connect, though the reverse also works.

Because socket connections need time, a publisher may send messages before a subscriber is ready; synchronization mechanisms (delays, sleep, or application‑level handshakes) are required to avoid loss.

A subscriber can connect to multiple publishers; ZeroMQ uses fair‑queuing to prevent message starvation.

If a publisher has no subscribers, its messages are silently dropped.

Other Valid Socket Pairings

PUB‑SUB, REQ‑REP, REQ‑ROUTER, DEALER‑REP, DEALER‑ROUTER, DEALER‑DEALER, ROUTER‑ROUTER, PUSH‑PULL, PAIR‑PAIR are all supported connection‑binding combinations.

Key Considerations

When a client needs both PULL and SUB sockets, each socket must be polled separately because recv is blocking; using select or a poller is advisable.

ZeroMQ’s PLAIN security mechanism provides simple username/password authentication suitable for low‑security internal networks; set ZMQ_PLAIN_SERVER on the server and ZMQ_PLAIN_USERNAME / ZMQ_PLAIN_PASSWORD on the client.

Exercise

Consider scaling a request‑reply system by inserting a router between clients and servers to distribute load and allow dynamic addition of server nodes.