Question

I was reading up on ActiveMQ which seems like a great implementation of a servicebus where producers can post messages and other processes can receive them.

However when reading the documentation, it looks like the producer has to give the ‘endpoint’ when sending a message.

I would rather have it the other way around: My producer posts events ‘import job starting’, ‘import job finished’, etc
and any consumer which is interested in certain classes of events can subscribe and receive these. However the consumer should not consume the event in that it doesn’t get send to other subscribers anymore.

What would be the best product to have this kind of property?

Constraints:
– It should have interfaces for at least .Net and php
– It should work across machine boundaries

Thanks

Answer 1

I think you are currently publishing to a queue which typically means that 1 consumer would, well, consume the message and the event is handled. If you need to have more then 1 consumer receiving the events, you should use topics.

When using Topics, all subscribed consumers receive the event you have posted.

Take a look at this: http://activemq.apache.org/how-does-a-queue-compare-to-a-topic.html