Delivery & reliability
Message ordering
Message ordering describes the sequence in which events are delivered or processed and the scope within which that sequence is meaningful, such as one connection or one entity.
Also found under: Event ordering, Sequence number
How it works
Transport order, publisher order and application completion order are different. Concurrent publishers and asynchronous handlers can create surprises even when a connection preserves its byte order. Use application versions when stale updates must not overwrite newer state, and fetch authoritative data if a sequence gap matters.
In a Pubb integration
Do not infer a global ordering guarantee across Pubb channels, publishers or reconnects. Include a record version in your payload if the interface must decide which update is newer.
Publish an eventA practical example
A task view has version 12 and receives a delayed version 11 update. It ignores that update and refreshes from the backend if it detects missing versions.