camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <>
Subject Re: Complex app… 1 context or many?
Date Sun, 08 Jan 2012 11:20:18 GMT
For bigger applications we also use multiple contexts and bridge the
context via the Camel ActiveMQ component (batch and online requests) or via
the Camel VM component (only online requests).
By splitting it into smaller parts each context is easier to understand and
test. In addition, the development process scales better because each
developer has its own service/context/... with defined interfaces. My 0,02


On Sun, Jan 8, 2012 at 12:53 AM, Jason Dillon <> wrote:

> I'm wondering what the best practice is for a complex application, where
> many sub-systems (some related, some not) are using camel to process
> messages, if it is best to have all of them share the same single
> CamelContext or if its better to have more than one CamelContext to
> partition the systems?
> Any advise?
> --jason

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message