Hi, Jan. Thanks for the info. I didn’t mean multiple CamelContexts per app. I meant multiple (many) apps, each with one CamelContext and one Route - versus one app, with one CamelContext, with many Routes.
If I were running on a single host, I think I’d want to keep the number of apps down and see how much I can put into one CamelContext (one app). If I’m in a clustered environment, I of course have more flexibility and scalability. But even then, I wouldn’t want to create an app (with one CamelContext) per Route. Basically, I’ll just have to experiment. I was looking to see how 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: [email protected] 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 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 Gridinas napsal(a): > 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 JMS, and get it written to a central database or JMS. >> >> The messages are asynchronous and don't require a response or any processing. We just have to suck in all that data and write it out to a DB or JMS. >> >> It would be really nice to keep these 100 very simple routes in a single config / RouteBuilder. But that's not the smart thing to do... By the time you reach a 100 routes you'd probably need an app server and access to a cluster. But I don't think spinning up a new CamelContext / app for 100 single Routes is the way to go either. Or maybe it is? Maybe you containerize every single Route with Docker and manage it with Kubernetes (or whatever)? >> >> I guess I'm just looking to see if anyone has experimented with this and did some performance comparisons - like, how many Routes were you able to cram into your CamelContext / Spring Boot app before it started degrading? And how folks managed a scenario like this where they had to pull in data from many sources. >> >> If you don't have a cluster, and have to keep everything on a single beefy host, I guess the question is moot and you have to do as much as you can in one CamelContext until you hit a scalability limit... >> >> Thanks and have a good weekend. >> >> Ron
