Most modern messaging systems have a built-in way to do message
throttling. But I believe that would only be on the message server
receive side. If you need it on the send side then sticking a value in
memcached might be the most performant place to put that global state.
-James
On 01/26/2012 08:01 AM, Carl Jokl wrote:
I suppose that the whole Stateless push is also encouraged by
Stateless Session Beans too.
I suppose certain problems can be complicated by a need for some kind
of common state and can get in the way of parallelism. One example in
the system I currently work with is the need to have a limit on the
number of messages sent that are of a given category. Sending vast
numbers of messages can be scaled in parallel but it gets complicated
if the system must guarantee that no more than a given number of
messages of that category are sent because then a central count needs
to be kept and updated in a synchronized manner.
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
