Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

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()

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).

...

Sync : direct:// + 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)

vm://

Remark : This component cannot be used between different OSGI servers

    • With persistence

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

...

If you prefer to deploy routes on 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://

This component cannot be used between different OSGI servers

    • Between Within or between different instances of OSGI servers (SMX4)

...