...
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
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 + threads()
Sync
: direct:// : http://camel.apache.org/direct.html + threads()
...
- Same JVM but different CamelContext
This approach is suitable for solutions running in standalone mode or deployed in Web Application Server (different WAR/EAR)
Remark : This component cannot be used between different OSGI servers
- With persistence
JMS queue engine : jms:// + threads()
Activemq queue engine : activemq://
...
+ threads()
- Different JVM & CamelContext
When the infrastructure offers the possibility to deploy the application on several machines, then you can use the approaches presented at point 2.1before. That means means that you will deploy the same application on several nodes and in this case, we have competitor consumers. Depending on the load on the servers, messages can be consume by application 1 running on Server 1 instead of application 2 running on Server 2.
If you prefer to deploy routes on different servers having different CPU/memory, then you can use the following components
- Suitable for solutions running in standalone mode or deployed in Web Application Server (different WAR/EAR)
vm:// : http://camel.apache.org/vm.html
This component cannot be used between different OSGI servers
- Between different Within or between different instances of OSGI servers (SMX4)
nmr:// : http://camel.apache.org/nmr.html
Camel can be not only plugged on the NMR bus but can also use the clustering functionality offered by ServiceMix 4 ()
...