Introducing the Executor Bus Binding

The 3.9 release introduces a new type of bus, the executor bus, which allows work to be 'sent' to another thread for either intensive processing or for easy outbound gateway authoring.

Usecases

• Outbound gateways: send an outbound message to executor bus thread that performs a send or export to an outbound system.
• Analytically intensive processing: Do computationally intensive work without tying up the application's main processing thread.

The executor bus provides the application with a handle to an Acknowledger callback which ensures that processing is completed even in the event of failure.

See the Executor Binding documentation for additional details.

Easier Inbound Gateways

The 3.9 release makes it even easier to author inbound gateways to bridge from external systems in a guaranteed fashion.

New: The AepSendStabilityEvent

• This event allows threads injecting messages into an application from an external source to be asynchronously notified when the platform can guarantee its processing will be completed.
• Provides the ability to attach correlation data to the injected message to allow inbound threads to acknowledge upstream.

See Unsolicited Sends for additional details.

Configurable Message Routing Functions

This release introduces channel key functions which can be defined in configuration decoupled from application logic to allow for dynamic content based message routing.

Example:

<channel name="new-orders">
  <key>Events/[partition=hash(${orderId}, 20)]</key>
</channel>

The above config driven uses a hash function to partition new-orders traffic across 20 partitions (Events/1 through Events/2), all without having to change a line of application code.

Improvements and Bug Fixes

And as always many general improvements and bug fixes.