At thetrainline.com we are currently working hard at re-engineering our e-commerce retailing platform to streamline the development of new features. This will allow better product offerings, innovation in ticket delivery methods, enhanced payment options and, above all, a cutting edge mobile experience. While our current platform is serving us well, as with all technological platforms, it is slowly becoming outdated and increased coupling is creeping in. As a result, our ability to change has been slowing down and this is not something we are ready to accept.
As part of the re-engineering work, we have been ramping up our use of RabbitMQ as a messaging infrastructure to build components for our new platform. While most of us are already familiar with building event-driven applications using NServiceBus/MSMQ, designing applications to communicate over RabbitMQ has its own unique challenges.
Here is a presentation from one of our weekly brown-bag tech talk sessions about some of the key considerations when developing new components leveraging RabbitMQ.