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-04-17 UTC."],[[["The latest version available is 2.37.0-rc, with links to documentation for versions back to 2.11.0."],["The content focuses on `MessageOrderingOption` in the `google::cloud::pubsub` namespace, outlining its role in guaranteeing message order."],["Message ordering ensures messages are received in the same order they are sent, requiring the client library to wait for successful delivery of batches."],["Message ordering is disabled by default because it can limit throughput for applications that don't need it."],["Detailed information about message ordering can be found in the `Publisher` class documentation."]]],[]]
