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 of the `MessageOrderingOption` is 2.37.0-rc, and it is the most current version of the google pubsub option."],["This page provides a historical overview of different versions of the `MessageOrderingOption`, including everything from 2.11.0 up to 2.37.0-rc."],["Message ordering in the `Publisher` class is disabled by default because it can limit the overall throughput of messages if not needed."],["Message ordering ensures messages are received in the order they were sent, but the client library has to wait for a batch of messages to be delivered before sending another."],["`MessageOrderingOption` type is an alias of bool."]]],[]]
