Building on what Claus said regarding 'deployment unit', I deploy my
'application' to Apache Karaf. In total it consists of 17 bundles(contexts)
containing 642 routes. How you organize it all is going to depend on what
makes sense for your application to be able to start/stop and update
independen
Hi
Camel has no limitations on the number of routes per context. However
you should have 1 camel context per "app" (deployment unit), so they
have the same lifecycle etc.
So a rule of thumb is to have routes that belong together, and share
same lifecycle / change together in your app.
So if your
onnect App
>
> -- Original Message --
>
> From: Jan Bednář
> To: users@camel.apache.org
> Sent: September 28, 2019 at 12:42 PM
> Subject: Re: One CamelContext vs. multiple CamelContexts
>
> Hi Ron, Mixing multiple CamelContext per application is not recomended
>
others
approached this and what they found. (Mantas said his group put 400 routes in a
single context!)
Thanks again.
Ron
Sent from Xfinity Connect App
-- Original Message --
From: Jan Bednář
To: users@camel.apache.org
Sent: September 28, 2019 at 12:42 PM
Subject: Re: One CamelContext vs
Hi Ron,
Mixing multiple CamelContext per application is not recomended approach.
Also support for multiple contexts is removed in Camel 3:
https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_multiple_camelcontexts_per_application_not_supported
Dne 27.9.2019 v 21:19 Mantas Gridi
You're going to be fine. My current project runs 400+ routes in single context.
On Fri, Sep 27, 2019 at 7:14 PM Ron Cecchini wrote:
>
> TL;DR: 1 CamelContext with 100 Routes vs. 100 CamelContexts each with 1 Route
>
> Say I need to ingest data from a hundred sensors or data sources, over TCP or
