Page History

...

This approach allows to distribute the load between different endpoints. The from endpoint plays the role of a 'proxy' when we use by example a jetty server

loadbalance() : http://camel.apache.org/load-balancer.html^{Image Removed}

Clustering

The clustering can be achieved in different ways : Work distribution,

...

Consumer competition,

...

...

...

depending how you would like to configure your infrastructure (one or several instances running on the same machine or distribute across a cloud of servers).

• Same JVM & CamelContext

Different Camel components can be used depending if the work must be done in a sync or async way

• • Without persistence

Async
: seda:// : http://camel.apache.org/seda.html^{Image Removed} + threads()

Sync
: direct:// : http://camel.apache.org/direct.html^{Image Removed} + threads()

• • With persistence

JMS queue engine : jms://

...

+ threads()
Activemq queue engine : activemq://

...

+ threads()

• Different JVM & CamelContext

...

• • Suitable for solutions running in standalone mode or deployed in Web Application Server (different WAR/EAR)

vm:// : http://camel.apache.org/vm.html^{Image Removed}

This component cannot be used between different OSGI servers

• • Between different instances of OSGI servers (SMX4)

nmr:// : http://camel.apache.org/nmr.html^{Image Removed}

Camel can be not only plugged on the NMR bus but can also use the clustering functionality offered by ServiceMix 4 ()

...