Using the source-oriented exchanges pattern to keep events in order - Alex Thomas

November 20, 2019

Almost every introduction to publish-subscribe technology embraces a model where different message types appear on correspondingly distinct topics. Unfortunately this introduces a rather fundamental flaw into common integration scenarios: it loses the order of events across the topics. The effects of this unintended re-ordering can be significant, forcing developers to implement elaborate workarounds. Using the "source-oriented exchanges" pattern, Alex will show how RabbitMQ offer a way to implement the equivalent of topics without losing track of the overall order of messages. -- RabbitMQ Summit 2019 connected RabbitMQ users and developers from around the world in London on 4 November, 2019. Learn what's happening in and around RabbitMQ, and how top companies utilise RabbitMQ to power their services. https://www.rabbitmqsummit.com RabbitMQ Summit was organised by: - CloudAMQP, offering fully managed RabbitMQ clusters https://www.cloudamqp.com - Erlang Solutions, offering world-leading RabbitMQ Consultancy, Support, Health Checks & Tuning solutions https://www.erlang-solutions.com/ RabbitMQ Summit 2019 was sponsored by the following companies. Platinum sponsors: Pivotal Oliver Wyman Gold sponsors: Nastel AWS Silver sponsor: Queue Explorer

Previous
Rapidly Building Event Driven and Streaming Applications with RabbitMQ - M. Sathe & M. Rosales
Rapidly Building Event Driven and Streaming Applications with RabbitMQ - M. Sathe & M. Rosales

In this session we explore a variety of modern event processing and streaming solutions built on top of Rab...

Next Video
How to use multiple RabbitMQ brokers with SpringBoot - Wander Costa
How to use multiple RabbitMQ brokers with SpringBoot - Wander Costa

How to connect your SpringBoot application to multiple RabbitMQ brokers? But why do you need multiple Rabbi...