Webinar

One of the original motivations for AMQP was the so-called middleware hell that had plagued organisations for decades due to the lack of open standards and the existence of proprietary and expensive message queuing products that did not interoperate, necessitating the development of adaptors and gateways that were costly to implement and maintain. However, while AMQP was originally conceived to help solve this existing problem, the protocol and products like RabbitMQ that evolved from it have largely been applied to solving new problems. This then raises the question as to whether RabbitMQ is equally applicable to the solution of traditional integration problems involving legacy software as it is to these newer problems. This talk will consider this question. The viability and benefits of replacing proprietary solutions with RabbitMQ will be considered. Challenges associated with such modernization initiatives will be discussed and solutions to some of these problems will be presented.

TARGET AUDIENCE

General audience. Most relevant to people interested in using RabbitMQ as an alternative to existing proprietary message queueing solutions in legacy environments.

OBJECTIVES 

To describe how RabbitMQ can be used to modernize legacy application environments.