jms - RabbitMQ Fanout Exchange (VirtualTopic Equivalent) -


i'm looking @ swapping out activemq rabbitmq few reasons. have multiple services each capable of publishing events (and publish events specific virtualtopic in amq). each of services capable of consuming messages other services. consumers set such subscribe consumer queue on virtualtopic.

this buys me ability fan messages out multiple queues (topic-like functionality) while keeping benefits of queues (load balancing , persistence).

it seems equivalent rabbitmq's fanout exchange. however, part found useful in activemq producer doesn't need have knowledge of consumers. publishes virtual topic. seems in rabbitmq, when exchange created, need definitive of queues publish message to.

tl;dr

is there routing scheme in rabbitmq equivalent activemq's virtual topic, such can produce messages topic distributed queue has been created off of virtual topic, without requiring hard-coded routing scheme somewhere in rmq?

i realized after posting question pretty trivial (not sure why never thought of before).

i looking @ wrong direction, wondering how automatically have publisher configure queues recipients - isn't right way approach question.

instead, have subscribers, when start up, bind exchange publisher users, provides in inversion of control i'm looking (publishers need not know consumers).


Comments

Popular posts from this blog

Android layout hidden on keyboard show -

google app engine - 403 Forbidden POST - Flask WTForms -

c - Why would PK11_GenerateRandom() return an error -8023? -