Hi Yeah that SEDA paper is famous http://en.wikipedia.org/wiki/Staged_event-driven_architecture
Its however written many years ago, when Java was not as evolved as today. Back in those days C++ was faster than Java. And today the story is different. Camel SEDA uses the JDK concurrency API and is thus not using home grown code. It only gets faster with each new version of Java. Also in Camel you only use SEDA "stages" when you send to a SEDA endpoint. Which means that its NOT used for every single node in the route graph. Which means you have a good balance between stages and "route logic". On Thu, Apr 8, 2010 at 2:14 AM, vcheruvu <vid.cher...@macquarie.com> wrote: > > Hi, > > I came across site about SEDA implementation, > http://www.eecs.harvard.edu/~mdw/proj/seda/ . Does camel SEDA component > follow this model? If it does, author stated that "It is also worth noting > that a number of recent research papers have demonstrated that the SEDA > prototype (in Java) performs poorly compared to threaded or event-based > systems implemented in C....... Also, SEDA imposes a high context switch > overhead in certain cases, depending on the number of threads and stages > used, and the processing granularity within each stage. " Is this still a > concern with SEDA implementation in Camel? > > Kind regards, > -Vid- > -- > View this message in context: > http://old.nabble.com/SEDA-implementation-tp28172153p28172153.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
