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."],[[["This webpage provides documentation for various versions of the Google Cloud Pub/Sub C++ library, ranging from version 2.11.0 to the latest release candidate 2.37.0-rc."],["The documentation covers the `MessageOrderingOption` struct, accessible for each listed version, allowing users to review changes or features across specific releases."],["Message ordering, a feature within the `Publisher` class, is discussed, which ensures messages are delivered in the same sequence they were sent."],["Message ordering is disabled by default, because it can reduce throughput for applications that do not require it."],["The `MessageOrderingOption` is an alias for the `bool` type."]]],[]]
