with hornetQ Messages are always processed / filtered on the server. It would be a waste of network resources to process them at the client.
Brilliant! - and thanks for the speedy reply
As a follow-up, the article I linked questions if it's better to have:
- fewer Topics with more message selectors
- or more Topics with fewer message selectors
Which is better for HornetQ?
I'm not sure I can give you a pre-formated answer here, It depends on a lot of factors.. it really depends.
You probably are talking about fewer topic subscriptions or more topic subscriptions. I don't see an issue with that.. HornetQ scales really well horizontally but as with any system you need to be careful with how you implement it. I suggest you test it well with your architecture.
I really meant number of topics (not number of subscriptions), but by your response, I take it that number of subscriptions is the larger scaling concern (native thread per subscription?). I suppose that more topics implies more subscriptions, unless we use hierarchical topics, in which case the number of subscriptions (per client) would remain const.
We're gearing up for tests, you're absolutely right to point that out
PS: congrats on the promo!
It will be a matter of your hardware / sizing then. It will be more up to hardware capacity than anything else.
Thanks BTW :-)