Home/ Questions/Q 7734893
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T07:21:53+00:00

My idea is to use camel to decouple modules. In order to support scalability

  • 0

My idea is to use camel to decouple modules. In order to support scalability and failover, I am wondering if the following architecture is adviced?

I have two applications with Camel embedded AppCamel1 and AppCamel2. Then I have standalone camel nodes Camel1 and Camel2.

AppCamel1 would have a route with fail-over/load balancing to Camel1 and Camel2. This way, if Camel1 crashes for example, Camel2 is used for failover.

Camel1 and 2 would do a REST call with the http component for example. Also there would be a request-reply from AppCamel1 up to camel1 or 2.

Is it a valid scenario?

What should I use to interconnect the different Camel instances (AppCamel1 to Camel1 or 2)? (I would like to know if it’s possible to avoid another component like a jms server in the middle)

Thank you!

Edited following Boday’s answer

the REST calls are from Camel1/2. I’d like to interconnect AppCamel1/2 to Camel1/2 and see if I can avoid anything in between. I guess mina is a possibility or even http but in that case a AppCamel1 and AppCamel2 need to know Camel1/2 which is not so good.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is also being discussed at the Camel mailing list, where there is also some pointers and suggestions
    http://camel.465427.n5.nabble.com/scalable-bus-with-multiple-Camel-instances-tp5606593p5606593.html

    • 0