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 different versions of the Google Cloud Pub/Sub C++ client library, starting from version 2.11.0 up to the latest release candidate 2.37.0-rc."],["The documentation specifically covers the `MessageOrderingOption` in the `google::cloud::pubsub` namespace, which relates to message ordering within the Publisher."],["Message ordering ensures that messages are received by the service in the same sequence as they were sent by the application, requiring the client library to wait for successful batch delivery before proceeding."],["Message ordering is disabled by default because it may limit the throughput for applications that do not need it, which is a behavior that can be modified by referring to the `Publisher` class documentation."],["The Type Alias of `MessageOrderingOption` is `bool`."]]],[]]
