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-14 UTC."],[[["The webpage provides documentation for different versions of the `MessageOrderingOption` in the Google Cloud Pub/Sub C++ library, ranging from version 2.11.0 to the latest release candidate 2.37.0-rc."],["Message ordering ensures that messages are received in the same order they are sent by a publisher, requiring the client library to wait for batch delivery before sending the next batch."],["The `MessageOrderingOption` feature is disabled by default, as it can limit throughput for applications that do not require message ordering."],["Detailed information about message ordering can be found in the `Publisher` class documentation."],["The type alias of the `MessageOrderingOption` is a `bool` data type."]]],[]]
