To guarantee messages are received by the service in the same order that the application gives them to a publisher, the client library needs to wait until a batch of messages is successfully delivered before sending the next batch, otherwise batches may arrive out of order as there is no guarantee the same channel or network path is used for each batch.
For applications that do not care about message ordering, this can limit the throughput. Therefore, the behavior is disabled by default.
See Also
the documentation for the Publisher class for details.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-05 UTC."],[[["This page lists different versions of the `MessageOrderingOption` documentation, ranging from the latest release candidate version 2.37.0-rc down to version 2.11.0."],["The latest stable version is 2.36.0, while the newest release candidate is 2.37.0-rc."],["Message ordering is disabled by default due to potential throughput limitations, but can be enabled to guarantee the same message order from application to service."],["Enabling message ordering requires the client library to ensure each batch is successfully delivered before sending the next, which may affect performance if not needed."],["The `Publisher` class documentation provides more information about the details of message ordering."]]],[]]