Asynchronous Publishing

The Micro-Integration for Databricks Zerobus supports asynchronous publishing only. Synchronous publishing is not supported.

Asynchronous publishing allows the Micro-Integration to process new messages without the need to wait for the previous message’s publish acknowledgment. While this can boost performance, it does come with a trade-off, as it may increase the chances and volume of duplicate messages.

A workflow can be configured to wait for the publisher's acknowledgments, asynchronously with the following configuration options:

# <workflow-id> : The workflow ID ([0-19])

solace.connector.workflows.<workflow-id>.acknowledgment.publish-async 
solace.connector.workflows.<workflow-id>.acknowledgment.back-pressure-threshold 
solace.connector.workflows.<workflow-id>.acknowledgment.publish-timeout        

See the Workflow Configuration Options table for details and default values of those configuration options.

In general, reducing the publish-timeout option increases the probability of duplicate message deliveries, while increasing the back-pressure-threshold option is likely to result in a higher occurrence of duplicate messages.