>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #1831250. --> Reported by: [sirup](https://www.drupal.org/user/2321604) >>> <p><strong>Description: </strong>This is a module intended for developers that want to use a message broker in combination with drupal. It allows you to send and receive messages without caring about the underlying technical challenges.</p> <p>Possible use cases include synchronizing drupal sites, integrating external systems, implementing distributed business logic or seperating heavy processing tasks from your normal drupal requests.</p> <p><strong>Project page:</strong> <a href="http://drupal.org/sandbox/sirup/1807310">Message Broker</a></p> <p><strong>Repo: </strong><code>git clone --branch 7.x-1.x http://git.drupal.org/sandbox/sirup/1807310.git message_broker</code></p> <p><strong>Intended for Drupal 7</strong></p> <p><strong>Similar modules</strong></p> <p>There are two similar modules: <a href="https://www.drupal.org/project/rabbitmq">RabbitMQ</a> and <a href="https://www.drupal.org/project/amqp">AMQP</a>. This are the differences:</p> <ul> <li>both modules are tied to amqp, this module is more generic and would allow to plugin other protocols like STOMP (the dummy module proves that this is already possible)</li> <li>this module stores the routing configuration in simple json files, allowing to reuse the file in other non-drupal applications (which is essential in many distributed systems)</li> <li>we allow to test AMQP messaging in-memory via our unique dummy module</li> <li>amqp module in detail <ul> <li>the module is only available for Drupal 6.x</li> <li>it adapts the Drupal Queue interface, which has its advantages but also throws away the power of the AMQP concepts: AMQP allows much more powerful things than queuing</li> <li>even the queueing implementation is not finished, because the drupal queue interface can not be mapped easily on the AMQP concepts</li> <li>besides the name, it actually uses the RabbitMQ product directly via a http interface that is not available when using other amqp products</li> </ul> </li> <li>rabbitmq module in detail <ul> <li>the module also adapts the queue interface from drupal with the same limitations</li> <li>not usable in combination with non-PHP systems or legacy systems as it has many assumptions about the structure of messages and exchanges</li> </ul> </li> </ul> <p><strong>Conclusion:</strong> Both modules do provide only queuing functionality on top of Drupals queue interface. In contrast this module is a full messaging solution that could be used for queueing, but is not limited to this use case. See the project page for more examples.<br> In fact the module names are misleading, because the amqp module is tied to rabbitmq and the rabbitmq one is more generic than the name states.</p> <p><strong>Reviews of other projects</strong><br> <a href="http://drupal.org/node/1840698#comment-6739492">http://drupal.org/node/1840698#comment-6739492</a><br> <a href="http://drupal.org/node/1842792#comment-6744726">http://drupal.org/node/1842792#comment-6744726</a><br> <a href="http://drupal.org/node/1840692#comment-6739522">http://drupal.org/node/1840692#comment-6739522</a></p> <p><a href="http://drupal.org/node/1842792#comment-6741930">http://drupal.org/node/1842792#comment-6741930</a><br> <a href="http://drupal.org/node/1882080#comment-6915780">http://drupal.org/node/1882080#comment-6915780</a>, <a href="http://drupal.org/node/1882000#comment-6915796">http://drupal.org/node/1882000#comment-6915796</a> and <a href="http://drupal.org/node/1877836#comment-6915840">http://drupal.org/node/1877836#comment-6915840</a><br> <a href="http://drupal.org/node/1880120#comment-6915908">http://drupal.org/node/1880120#comment-6915908</a></p> <p><a href="http://drupal.org/node/1889164#comment-6942104">http://drupal.org/node/1889164#comment-6942104</a></p> <p>Thanks in advance</p>