Lesson 72 - Multi Broker Pattern

preview_player
Показать описание
Рекомендации по теме
Комментарии
Автор

Thanks for the video. How this pattern could be adapted for IoT hub and multiple consumers/producers? The challenges here are the number of simultaneous tcp connections from the devices, the number of ingested messages and the need of a device to subscribe to topics. Maybe an idea for a next episode

mqtt
Автор

Dear Marc, thank you for this interesting pattern. But honestly, I see some weaknesses here. Scalability and Agility. Why EventProducer1 should increase additional complexity by using multiple channels if it's been worked fine for a long time? Just because there are new EventProducer2 and EventProducer3 has appeared? But what if there will appear EventProducer6...9 next month? It seems all event producers get externally coupled via channels? How to scale them independently form each other?
The next concern is about the number of channel endpoints and channel types. There is just one channel type, right? What if some event producer decides to switch to another type of broker? Should remaining event producers and consumers update themselves or they will keep using redundant channel instances? They stop being autonomous.

anatoliyrozhyn
Автор

First of all thanks for this nice video. I am struggling to implement in practicality. our spring application is configured with one rabbitmq broker only there is no such configuration where I can configure multiple rabbit mq and every message will be broadcast to all brockers.

ekusimmu