Hi To clarify the subject: with "stateful" I mean processors with an internal state like aggregator, resequencer etc. On the other hand would I call processors like content based router etc. as stateless because they can take a single message and process it without further need to wait for other messages.
Is it correct that a route with only stateless processors scales more or less proportional with the number of concurrent consumers? And what happens with concurrent consumers when I insert a stateful processor like an aggregator? these processors must "synchronize" all consumers to do their work, are they? So how can I scale such processors? I could of course make multiple identical aggregator routes and dispatch messages across them (for example round robin). That would mean I get more aggregations since they work completely individual. Is this the best way to do it or is there some kind of processor internal scaling that can configured? Because this solution needs an implementation change, while scaling with concurrent consumers is just a configuration change. Thanks for your answers Stefan
