Message Ordering
In Data Orchestrator, transports are given the task to deliver messages in a well-known AMQP structure. The ordering of such messages is then preserved on a set of criterias:
- There is no such thing as "in-order" among devices. A message X sent to device A can be processed after a message Y sent to device B even if Y was ingested in the AMQP queue before X. This is intentional and by design.
- All messages to a specific device A are always guaranteed to be processed in the very same order of the transport ingestion.
- Ordering is not dependent on the message timestamp, which can be set by different sources (depending on the interface's definition of timestamp).
- Responsibility of message ordering before entering AMQP is entirely up to the transport.
- Message ordering concerns only pipelines in the DUP, including but not limited to data ingestion in the Database and Simple Triggers.