Toward a Commodity Enterprise Middleware

Abstract

AMQP (Advanced Message Queuing Protocol) was born out of my own experience and frustrations in developing front-and back-office processing systems at investment banks. It seemed to me that we were living in integration Groundhog Day-the same problems of connecting systems together would crop up with depressing regularity. Each time the same discussions about which products to use would happen, and each time the architecture of some system would be curtailed to allow for the fact that the chosen middleware was reassuringly expensive. From 1996 through to 2003 I was waiting for the solution to this obvious requirement to materialize as a standard, and thereby become a commodity. But that failed to happen, and I grew tired of waiting. Consequently, AMQP was created and had its first mission-critical deployment to production in mid-2006. That project paid for itself with its first deployment, serves 2,000 users, and processes 300 million messages per day. This article sets out the motivations, capabilities, and credentials of AMQP and offers it as a practical solution for a standards-based messaging infrastructure. AMQP is a binary wire protocol and well-defined set of behaviors for transmitting application messages between systems using a combination of store-and-forward, publish-and-subscribe, and other techniques. 1 I use the term application messages to distinguish AMQP from instant messaging or other forms of end-user messaging. AMQP addresses the scenario where there is likely to be some economic impact if a message is lost, does not arrive in a timely manner, or is improperly processed. The protocol is designed to be usable from different programming environments, operating systems, and hardware devices, as well as making high-performance implementations possible on various network transports including TCP, SCTP (Stream Control Transmission Protocol), and InfiniBand.

Enabling virtual collaboration in Digital Cultural Heritage in the SEEM region

“…The role of a message broker is to mediate the communication between applications [20,26,38]; this is done by validating, transforming and routing messages. RabitMQ implements the Advanced Message Queuing Protocol (AMQP) [22]. In the case of Clowder, any extractor that is implemented must register one or more delivery queues on RabbitMQ the moment it is activated.…”

Evaluation of highly available and fault-tolerant middleware clustered architectures using RabbitMQ

“…The exchange looks at the information in the headers of a message and selects where they should be transferred to. This is how AMQP brings the various messaging idioms together -clients can select which exchange should route their messages [15].…”

WPSS: watching people security services

“…But it can also be used with GPS systems for outdoor tracking, or in a retail environment where satellite reception is possible, for instance a shopping mall with a glass roof. For live import of realtime data, TrackLab uses the Noldus Communication Framework (NCF), which is a thin wrapper around RabbitMQ, an implementation of the Advanced Message Queuing Protocol (AMQP) [21]. As such NCF enables the setup of a flexible and scalable distributed system, i.e.…”