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-04-17 UTC."],[[["The latest version available is 2.37.0-rc, with numerous other versions, such as 2.36.0, 2.35.0, and so on, down to 2.11.0, also listed."],["The document describes how to guarantee that messages are received by the service in the same order they were sent, requiring a wait for batch delivery before sending the next batch."],["Message ordering can limit throughput, and is therefore disabled by default."],["The documentation also offers detailed information about the `Publisher` class."],["The message ordering functionality uses a `bool` type alias."]]],[]]
