Hi You can use in-memory only communication across JVMs such as hazelcast
Jean wrote a blog about this http://blog.nanthrax.net/2012/02/communication-between-two-remote-camel-routes-using-karaf-cellar/ There is also DOSGi - distributed osgi. But that of course requires OSGi. There is a really fast implementation in Fuse Fabric: http://gnodet.blogspot.se/2011/06/distributed-osgi-in-fabric.html And I think there is a DOSGi implementation in Apache CXF. And speaking of Fuse Fabric, then it will offer more easy to configure, manage, clusters of JVMs. Which discovery and failover, and all the stuff like that. https://github.com/fusesource/fuse At Apache we have many links to various blogs and articles, there is some great ones among them. http://camel.apache.org/articles On Mon, Apr 2, 2012 at 7:00 PM, Christian Müller <christian.muel...@gmail.com> wrote: > It's not "Camel mainly makes sense with a broker like ActiveMQ". There are > many other easons why you should use Camel also without a message broker. > I want only let you know > 1) what the benefit of a message broker is and > 2) what customers says is sometimes not what they really want... ;-) > > Best, > Christian > > On Mon, Apr 2, 2012 at 4:25 PM, unludo <unl...@gmail.com> wrote: > >> I see that Camel mainly makes sense with a broker like ActiveMQ, as a core >> for a scalable/decoupled system. >> >> Thanks for helping me understanding this! >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/scalable-bus-with-multiple-Camel-instances-tp5606593p5612599.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> -- Claus Ibsen ----------------- CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
