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."],[[["The latest version available is 2.37.0-rc, with numerous prior versions dating back to 2.11.0 also accessible."],["This page focuses on the `MessageOrderingOption` for Google Cloud Pub/Sub, which is found in the `google::cloud::pubsub` namespace across the different versions."],["Message ordering guarantees that messages are received in the same order they are sent, which can decrease throughput as batches need to be delivered in full before the next is sent."],["Message ordering behavior is disabled by default to avoid limiting throughput for applications that do not require this guarantee."],["More details on message ordering can be found in the documentation for the `Publisher` class, with the `MessageOrderingOption` type alias being of type `bool`."]]],[]]
