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."],[[["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 the latest release candidate 2.37.0-rc."],["The `MessageOrderingOption` controls whether messages are guaranteed to be delivered to the service in the same order they were sent by the publisher, which may impact throughput."],["Message ordering is disabled by default, as it can limit throughput for applications that do not require it, by requiring the client library to wait for a batch of messages to be successfully delivered before sending another."],["Detailed information about message ordering and how to enable it can be found in the documentation for the `Publisher` class, which is linked in the page."],["The type alias for `MessageOrderingOption` is `bool`."]]],[]]
