Book Image

ZeroMQ

By : Faruk Akgul
Book Image

ZeroMQ

By: Faruk Akgul

Overview of this book

<p>ØMQ (also spelled ZeroMQ, 0MQ, or ZMQ) is a high-performance asynchronous messaging library aimed at use in scalable distributed or concurrent applications. It provides a message queue, but unlike message-oriented middleware, a ØMQ system can run without a dedicated message broker. The library is designed to have a familiar socket-style API.<br /><br />"ZeroMQ" teaches you to use ZeroMQ through examples in C programming language. You will learn how to use fundamental patterns of message/queuing with a step-by-step tutorial approach and how to apply them. Then, you’ll learn how to use high level APIs and to work with multiple sockets and multithreaded programs through many examples.<br /><br />This book looks at how message/queue works in general and what kinds of problems it solves. Then, it explains how ZeroMQ works and how it differs from other message/queue libraries and how it can be used in different scenarios.<br /><br />You will also learn how to apply essential message/queue design patterns in different scenarios, and how they differ from each other. It shows you practical examples you can apply. You will also learn how to work with multiple sockets.<br /><br />You will learn the basics of ZeroMQ as well as how to use different patterns.</p>
Table of Contents (12 chapters)

ZeroMQ sockets


ZeroMQ sockets have four different methods, just like normal sockets, as we have said at the beginning of this chapter. It should be noted that ZeroMQ sockets are always void pointers and are asynchronous.

Differences between TCP sockets and ZeroMQ sockets

The following is the difference between TCP sockets and ZeroMQ sockets:

  • ZeroMQ sockets are asynchronous.

  • They may implement particular patterns.

  • TCP sockets are one-to-one whereas ZeroMQ sockets are many-to-many. However, you could implement one-to-many, one-to-one, many-to-one, or many-to-many with ZeroMQ, depending on your needs and socket type.

  • ZeroMQ sockets transmit messages whereas TCP transmit bytes. As we said in Chapter 1, Getting Started, a message is a fixed-length binary object.

  • I/O is done in the background in ZeroMQ sockets. Even if your application is too busy to handle messages, they are put in queues.

  • Unlike TCP, ZeroMQ sockets do not care whether the destination exists or not.

  • ZeroMQ sockets may transmit data to...