netwyman

ZeroMQ is a library used to implement messaging and communication systems between applications and processes - fast and asynchronously. If you have past experience with other application messaging solutions such as RabbitMQ, it might come a little bit challenging to understand the exact position of ZeroMQ. When compared to some much larger projects, which offer all necessary parts of enterprise messaging, ZeroMQ remains as just a lightweight and fast tool to craft your own. ZeroMQ Socket Types ZeroMQ differs in the way its sockets work. Unlike the synchronous way the regular sockets work, ZeroMQ’s socket implementation “present an abstraction of an asynchronous message queue”. The way these sockets work depend on the type of socket chosen. And flow of messages being sent depend on the chosen patterns, of which there are four: Request/Reply Pattern: Used for sending a request and receiving subsequent replies for each one sent. Publish/Subscribe Pattern: Used for distributing data fro...

Basically Pub/sub is shorthand for publish/subscribe messaging, an asynchronous communication method in which messages are exchanged between applications without knowing the identity of the sender or recipient. Basic Concept of pub/sub: Four core concepts make up the pub/sub model: Topic   – An intermediary channel that maintains a list of subscribers to relay messages to that are received from publishers Message   – Serialized messages sent to a topic by a publisher which has no knowledge of the subscribers Publisher   – The application that publishes a message to a topic Subscriber   – An application that registers itself with the desired topic in order to receive the appropriate messages How Pub/Sub Works In the overview we covered how a publisher sends a message to a topic and how the topic forwards the message to the appropriate subscriber. From a topology point of view it is a simple process. When it comes to coding the publish or the subscribe process the mod...