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-21 UTC."],[[["The latest available version is 2.37.0-rc, with links provided for older versions, down to 2.11.0, of the C++ Pub/Sub library documentation."],["This documentation focuses on `MessageOrderingOption` within the Google Cloud Pub/Sub C++ library."],["Message ordering is a feature that ensures messages are received in the order they were sent, but it is disabled by default due to potential throughput limitations."],["Enabling message ordering requires the client library to wait for successful delivery of each batch of messages, however the same channel or network path is not guaranteed for every batch."],["The documentation also includes a link to the `Publisher` class for additional information about message ordering."]]],[]]
