You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Jason Dillon <ja...@planet57.com> on 2012/01/08 00:53:46 UTC
Complex app… 1 context or many?
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
Re: Complex app… 1 context or many?
Posted by Fernando Ribeiro <we...@fernandoribeiro.eti.br>.
I do usually keep them separate, unless they really need to share context.
Regards.
On Jan 7, 2012 9:54 PM, "Jason Dillon" <ja...@planet57.com> 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
Re: Complex app… 1 context or many?
Posted by Jason Dillon <ja...@planet57.com>.
Wow... a context for a context... brain explodes.
I didn't know this was here I'll have a deeper look once my brain is back in one piece ;-)
--jason
On Jan 8, 2012, at 5:08 AM, Willem Jiang wrote:
> You can have a look at the camel-context component[1]. It maybe useful for you have a try :)
>
> [1]http://camel.apache.org/context.html
>
> On 1/8/12 7: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
>
>
> --
> Willem
> ----------------------------------
> FuseSource
> Web: http://www.fusesource.com
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.javaeye.com (Chinese)
> Twitter: willemjiang
> Weibo: willemjiang
Re: Complex app… 1 context or many?
Posted by Willem Jiang <wi...@gmail.com>.
You can have a look at the camel-context component[1]. It maybe useful
for you have a try :)
[1]http://camel.apache.org/context.html
On 1/8/12 7: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
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
Re: Complex app… 1 context or many?
Posted by Jason Dillon <ja...@planet57.com>.
Thanks everyone for the feedback.
--jason
On Jan 8, 2012, at 3:20 AM, Christian Müller wrote:
> 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
> $...
>
> Best,
> Christian
>
> On Sun, Jan 8, 2012 at 12:53 AM, Jason Dillon <ja...@planet57.com> 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
Re: Complex app… 1 context or many?
Posted by Christian Müller <ch...@gmail.com>.
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
$...
Best,
Christian
On Sun, Jan 8, 2012 at 12:53 AM, Jason Dillon <ja...@planet57.com> 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