Message Batching

Messages are processed in batches on the consumer side. The optimal configuration depends on the specific use case.

The main consideration when deciding the size of the batch size is that a larger batch size can improve throughput but could lead to higher number of duplicates.

We recommend that you test different configurations to determine the optimal settings for your use case. For more information, see the section on binder configuration options for available options and default values.

The batch size can be configured to 1 to disable batching. It's important to note that all messages in the batch are rejected if both the following conditions exist:

• The batchMaxSize is more than 1.

• An error occurs during the processing of any message within the batch.

For example, if you have a batch of 50 messages and one message fails, all 50 messages in the batch are rejected.

For more information, see Snowflake Binder Configuration Options.

Batching and Metrics

The solace.connector.process and solace.connector.error.process metrics apply to batches. These metrics are incremented once per batch, not once per message. To get a count of number of messages processed, use the solace.connector.publish.ack metric.

For more information, see Managing Metrics.