concept publishing in category rabbitmq

appears as: publishing, publishing
RabbitMQ in Depth

This is an excerpt from Manning's book RabbitMQ in Depth.

Method frames carry with them the class and method your RPC request is going to make as well as the arguments that are being passed along for processing. In figure 2.5, the method frame carrying a Basic.Publish command carries the binary packed data describing the command, and the request arguments that are passing along with it. The first two fields are numeric representations of the Basic class and the Publish method. These fields are followed by the string values for the exchange name and the routing key. As previously mentioned, these attributes instruct RabbitMQ on how to route a message. The mandatory flag tells RabbitMQ that the message must be delivered or the publishing of the message should fail.

Although not every system has such hard requirements around message delivery guarantees as banking applications do, it’s important for software like RabbitMQ to ensure the messages it receives are delivered. The AMQP specification provides for transactions in message publishing, and for the optional persistence of messages, to provide a higher level of reliable messaging than normal message publishing provides on its own. RabbitMQ has additional functionality, such as delivery confirmations, that provide different levels of message delivery guarantees for you to choose from, including highly available (HA) queues that span multiple servers. In this chapter you’ll learn about the performance and publishing guarantee trade-offs involved in using these functionalities and how to find out if RabbitMQ is silently throttling your message publisher.