Yes, it depends on how many concurrentConsumers you have. Default is 1. And yes, if you use direct component with 5 separate application threads calling into the route, you won't need context switching and blocking queues.
Take a good look at SEDA ( http://en.wikipedia.org/wiki/Staged_event-driven_architecture, as well as the camel-seda component referenced by Claus above...) to see when it becomes advantageous. On Wed, May 29, 2013 at 8:05 AM, anand_tech <anand29...@gmail.com> wrote: > Thanks for quick response > > so at the end it boils to how much concurrentConsumers i have configured on > seda endpoint. And i mentioned "one" because i haven't configured any > concurrentConsumers in my code as of now, so there would be only one seda > thread processing all the exchanges rite ? > > And one more question : if i change this seda to direct component then all > 5 > different threads will now be processed concurrently since direct is like > method invocation : no blocking queue and async stuff. Please correct me. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Back-to-Basics-Apache-Camel-Routes-and-Direct-Component-tp5731899p5733419.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
