This example shows several examples of Load Balancer EIP with Apache Camel application using Spring Boot.
-
Round-robin - The exchanges are selected in a round robin fashion. This is a well known and classic policy, which spreads the load evenly.
-
Random load - 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)
-
Failover - In case of failures the exchange will be tried on the next endpoint.
-
Weighted round-robin - The weighted load balancing policy allows you to specify a processing load distribution ratio for each server with respect to the others. In addition to the weight, endpoint selection is then further refined using round-robin distribution based on weight.
-
Custom - The preferred way of using a custom Load Balancer is to use this policy, as the ref attribute is not supported anymore.
If you hit any problem using Camel or have some feedback, then please let us know.
We also love contributors, so get involved :-)
The Camel riders!