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-05 UTC."],[[["This webpage provides documentation for different versions of the Google Cloud Pub/Sub C++ library, ranging from version 2.11.0 up to the release candidate 2.37.0-rc."],["The documentation details the `MessageOrderingOption` struct, which configures whether messages are delivered in the same order as they are given to the publisher."],["Message ordering is disabled by default to maximize throughput, as enforcing order can limit how many messages can be sent."],["The `Publisher` class documentation provides further information on the ordering of messages and configuration options."],["The `MessageOrderingOption` is an alias of the `bool` type."]]],[]]
