On Fri, Oct 8, 2010 at 6:25 PM, tide08 <sachin2...@yahoo.com> wrote: > > You are right Ashwin about design patterns, and that is why exactly I posted > here. It is typically not a load balancer scenario, I can create "n" routes > one each per uri but something similar to loadbalancer might have served > better. >
I would assume the load balancing could be part of the consumer (if it supported that). So you could configure the endpoint/consumer with the remote endpoints it should consume from. On a side note Camel provides a RoutePolicy which you can use as a sort of poor mans load balancer. Then you could define ex 3 Camel routes and have RoutePolicy act as load balancer by suspending/resuming the consumers. But I am sure there are better ways. > Thanks! > -- > View this message in context: > http://camel.465427.n5.nabble.com/Loadbalancer-for-consuming-tp3203497p3205012.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
