The platform includes several built in bus providers that can be used out of the box. The pages below discuss some of the specific consideration for each bus binding.  

JMS Binding

The JMS binding works with JMS 1.1 level JMS clients and is configured using JNDI lookup. In addition to JNDI lookup the platform provides a subclassed version of the JMS binding optimized for working with ActiveMQ. 

Loopback Binding

The platform's loopback binding can be used to send to other applications running in the same process, not across different processes. This binding is often used for unit testing in which several applications may be launched in the same process for easy debugging.

Solace Binding

The platform's solace binding includes both a java based and JNI-based implementation and allows connectivity to a solace message router https://solace.com/products/message-routers.

Executor Binding

The Executor Bus Binding is a special bus binding that allows applications to provide send work (via a message) to be processed on a separate thread. The executor binding can be used to perform processor intensive work in a thread other than an application's main dispatch thread, or can be used as a means to implement outbound gateways in which the executing thread 'pushes' the sent message to an external system. Work done by the processor of an executor bus is acknowledged and therefore Guarant

Kafka Binding

The Kafka provides messaging connectivity with Kafka Brokers. It is not currently documented as it is still in an incubation phase. If you are interested in using the Kafka binding, let us know mailto:contact@neeveresearch.com.