THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
So the above example will load balance requests from direct:start to one of the available mock endpoint instances, in this case using a round robbin policy.
For further examples of this pattern in use you could look at the junit test case
Build in load balancing policies
Camel has out of the box the following policies:
Type | Description |
Round Robin | The exchanges is selected in a round robin fashion. This is a well known and classic policy. This spreads the load even. |
Random | A random endpoint is selected for each exchange |
Sticky | Sticky load balancing using an Expression to calculate a correlation key to perform the sticky load balancing; rather like jsessionid in the web or JMSXGroupID in JMS. |
Topic | Topic which sends to all destinations (rather like JMS Topics) |
| Include Page | ||||
|---|---|---|---|---|
|