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."],[[["The latest version of the documentation available is 2.37.0-rc, with previous versions ranging down to 2.11.0 also accessible."],["The content focuses on `MessageOrderingOption` within the Google Cloud Pub/Sub C++ library, which deals with the order in which messages are processed and received."],["Message ordering is disabled by default, because enabling it can limit throughput as the client library needs to wait for each message batch to be successfully delivered before sending the next."],["Message ordering guarantees messages are received by the service in the same order they were provided to the publisher by the application."],["The `Publisher` class documentation provides more details about message ordering."]]],[]]
