ZeroMQ (Zero Message Queue)
Last Updated: July 29, 2026 | By Mihail Sebastian | AI Dictionary
A messaging library that moves data directly between processes without a central broker, used where distributed systems need low-latency communication.
What is ZeroMQ (Zero Message Queue)?
ZeroMQ (also written ØMQ) is a messaging library that lets programs send messages directly to each other over sockets, with no central broker in the middle. It gives distributed systems the patterns of a message queue at close to the speed of raw networking.
The “zero” signals what it removes: no broker to run, no server to administer. Each application links the library and talks straight to its peers.
How ZeroMQ Works
ZeroMQ sockets implement messaging patterns rather than raw connections. Publish/subscribe broadcasts data to any number of listeners, request/reply pairs a question with an answer, and push/pull spreads tasks across a pool of workers.
Bindings exist for most languages; PyZMQ, the Python binding, is what most ML tooling uses. The same code works across threads, processes, or machines by changing only the transport address.
Example of ZeroMQ
Jupyter is built on ZeroMQ. The notebook interface and the kernel that executes your code are separate processes: when you run a cell, the Jupyter server sends the code to the kernel over one ZeroMQ socket, while results, print output, and status updates stream back over others.
That is the library’s typical role in ML work. It is plumbing you rarely see, moving data between the pieces of a distributed system (worker processes feeding a training loop, services exchanging predictions) with minimal overhead.
Related AI terms: Jupyter Notebook · Parameter Server · Webhook · Pipeline
Did you like the ZeroMQ (Zero Message Queue) gist?
Learn about 250+ need-to-know artificial intelligence terms in the AI Dictionary.
Mihail Sebastian — Writes about AI governance, regulation, and the technology behind them. Placeholder bio — replace with a real credential line. About