A: Real-Time-Messaging is a nice tag, however You may soon realise, that once going into the territory of Real-Time, there is no justification for spending clock-cycles on wrapping any message into the XHTML-Matrjoska-in-Another-Matrjoska-inside-another-Matrjoska alike envelopes-inside-envelopes and associated inefficiencies. Real-Time struggles to operate in real time, so to spend/lose a minimum achievable time necessary to process … Read more
Trivial Archetypes ZeroMQ “sockets” are sounding alike a socket-oriented device, however on a closer look this smart library rather adds a Formal Communication Pattern ( which btw. uses a true socket ) that has a layered design to internally address details like internal elastic-buffering, internal 1:N Fair-Queue-Sending / Polling, internal ioThread load-balancing, to name just … Read more
Edit: My initial answer had a strong focus on AMQP. I decided to rewrite it to offer a wider view on the topic. These 3 messaging technologies have different approaches on building distributed systems : RabbitMQ is one of the leading implementation of the AMQP protocol (along with Apache Qpid). Therefore, it implements a broker … Read more
Well, ZeroMQ is a bit tricky to read as a socket-“counterparty” ( it’s not ) Why? Classical socket is a free-to-harness resource. ZeroMQ is a rather complex hierarchy of ideas and principles of behaviours ( better – distributed behaviours ), that help design smart distributed computing systems, without touching the low-level ( ZeroMQ well abstracted … Read more