S
saxo123
Hi folks,
let's say there were a situation like this: Some producers send
thousands of messages through a JMS system to some thousands
consumers. What is the best approach towards scalability?
1) 1 JMS publish-subscriber channel with one dispatcher at the end
that takes every msg from the channel and propagates it to the
respective consumer out of those thousand consumers
2) 1 JMS publish-subscriber channel where every consumer peeks a newly
arrived msg and checks whether it is for him and takes it from the
queue if so.
3) Many JMS publish-subscriber channels with one dispatcher for
everyone. I favour this one.
4) Thousand point-to-point connections. Sure not, I guess.
One problem that makes me think: If those dispatcher threads obtain
little CPU time the messages will sit in the queue and throughput will
go down. Making those dispatcher threads demon therads is all there is
to it?
One might say that I should go downtown and by a book about JMS.
Already did that, perused several books, acutally. They don't tell you
what approach works best in certain situations. It's like looking for
a book that tells you about good software design. They are almost
inexistent, as well ...
Thanks in advance.
Cheers, Oliver
let's say there were a situation like this: Some producers send
thousands of messages through a JMS system to some thousands
consumers. What is the best approach towards scalability?
1) 1 JMS publish-subscriber channel with one dispatcher at the end
that takes every msg from the channel and propagates it to the
respective consumer out of those thousand consumers
2) 1 JMS publish-subscriber channel where every consumer peeks a newly
arrived msg and checks whether it is for him and takes it from the
queue if so.
3) Many JMS publish-subscriber channels with one dispatcher for
everyone. I favour this one.
4) Thousand point-to-point connections. Sure not, I guess.
One problem that makes me think: If those dispatcher threads obtain
little CPU time the messages will sit in the queue and throughput will
go down. Making those dispatcher threads demon therads is all there is
to it?
One might say that I should go downtown and by a book about JMS.
Already did that, perused several books, acutally. They don't tell you
what approach works best in certain situations. It's like looking for
a book that tells you about good software design. They are almost
inexistent, as well ...
Thanks in advance.
Cheers, Oliver