No out of the box for this. Yeah a custom load balancer, or custom predicate for a content based router etc. Or a java bean for a recipient list can be used.
Or maybe look into trying to extend the Camel throttler and then do something else if the throttler limit is hit. Not sure how easy this code logic is to extend to do something else. On Fri, Nov 8, 2013 at 12:52 PM, Henryk Konsek <hekon...@gmail.com> wrote: > Hi guys, > > I've been asked about interesting Camel case and I don't know the answer :) . > > The problem that friend of mine is trying to address is that he wants > to send messages to persistent store A, but if we hit the throttling > limit, then he wants to send messages above the limit to message store > B. > > For example if throttling limit is 100 messages per second, and we > receive 300 messages during the second time frame, then we would like > to store only 100 messages in store A, and 200 in store B. > > The idea seems to be something between throttler and load balancer. > The one thing that comes to my mind here is to create custom load > balancer implementation with timeframe-based dispatching logic similar > to one used in throttler. Before I suggest this to him I want to be > sure that in fact Camel doesn't support this kind of balancing out of > the box. > > Thanks in advance. Cheers. > > -- > Henryk Konsek > http://henryk-konsek.blogspot.com -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
