You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi ,
I've been working with RawRabbit for a few weeks now , the project that I inherited was using 1.10 and I immediately upgraded to 2.0 RC . A couple of days ago we discovered why I could not reproduce the same behavior as before I began working on my project , which is that RawRabbit seems to create the queues differently in 2.0RC . In 1.10 , using the typed publish/subscribe calls , the queues are created per message , then per service I.E. object_created_service_1 . This is our desired design , as it allows for each service that is interested to receive every message of a given type .
On the other hand , in 2.0RC using the typed publish/subscribe calls , the queues are created per message I.E. object_created . In this approach only one service subscribed to a given message type will receive each published message .
Is there a way to configure RawRabbit that would allow us to revert to the queue generation from version 1 and continue to use the new features in version 2 ?
The text was updated successfully, but these errors were encountered:
Hi ,
I've been working with RawRabbit for a few weeks now , the project that I inherited was using 1.10 and I immediately upgraded to 2.0 RC . A couple of days ago we discovered why I could not reproduce the same behavior as before I began working on my project , which is that RawRabbit seems to create the queues differently in 2.0RC . In 1.10 , using the typed publish/subscribe calls , the queues are created per message , then per service I.E. object_created_service_1 . This is our desired design , as it allows for each service that is interested to receive every message of a given type .
On the other hand , in 2.0RC using the typed publish/subscribe calls , the queues are created per message I.E. object_created . In this approach only one service subscribed to a given message type will receive each published message .
Is there a way to configure RawRabbit that would allow us to revert to the queue generation from version 1 and continue to use the new features in version 2 ?
The text was updated successfully, but these errors were encountered: