Page History

ServiceMix allows for different message dispatch policies within the Normalized Message Router (NMR) Broker.
There are three basic types, that have different characteristics and are suited to different usage cases.

They are as follows:

ST Flow

Straight-throw flow. A MessageExchange is routed straight to it's destination with no staging or buffering. A straight through flow is best suited for the cases where the ServiceMix JBIContainer is deployed with simple flows (no state) or embedding, or where latency needs to be as low as possible.

Seda Flow

The SedaFlow introduces a simple event staging between the internal processes in the NMR Broker. A Seda flow (the default) is suited for general deployment, as the additional staging is well suited buffering exchanges between heavily routed to components (where state may be being used) for example.

JMS Flow

A JMS Flow is used for cases where you need collaboration between more than one ServiceMix JBIContainer (for fail-over or scalability).
Component deployment happens in the same way as a normal SericeMix JBI container (both for POJO and archive Component deployment) but all the containers in the cluster are notified of a deployment, and the JMS Flow will handle automatic routing (and failover) of MessageExchange(s) between the container instances.
A Message Queue is used for each Component instance, so multiple instances of the same named Component will have requests load balanced across them.