• Unlike TCP, ZeroMQ sockets do not care whether the destination exists
• ZeroMQ sockets may transmit data to multiple nodes and receive data from
We cannot start the source node and then the destination node when we work with
TCP sockets. This is because the source node would immediately try to connect to
the destination and if there was no destination present to receive the message, then
we would have a problem. However, in ZeroMQ, the message can be enqueued and
sent later if there is no destination to receive the message. Another difference is that
we tell ZeroMQ to send and receive messages instead of bytes.
ZeroMQ sockets are many-to-many
We will focus mainly on the unicast scheme, but there are other routing schemes
• Unicast : This is the major message transmission scheme among the other
routing schemes. It has a one-to-one relationship where the source transmits
a message to only one destination.
• Multicast : This is a one-to-many approach where one source transmits
messages to many destinations, which are subscribed to the source. It does
not guarantee the delivery of messages to the destinations, just like UDP.