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-21 UTC."],[[["This webpage provides documentation for the `MessageOrderingOption` in various versions of the Google Cloud Pub/Sub C++ client library, ranging from version 2.11.0 to 2.37.0-rc."],["Version 2.37.0-rc is the latest release candidate, with 2.12.0 being the base version for which additional information is available."],["The `MessageOrderingOption` feature, disabled by default, guarantees that messages are received in the same order they were sent, and this function is achieved by waiting for successful delivery of each batch before sending another."],["The documentation also refers users to the `Publisher` class for further details regarding message ordering, where `MessageOrderingOption` is a type alias for `bool`."],["Applications that do not require message ordering can experience reduced throughput."]]],[]]
