Looking at Pub/Sub documentation and the new cloud console I noticed a reference to message ordering
tl;dr it looks like a key can be added to ensure that messages are pulled/pushed to subscribers in the same order pub/sub receives the.
But that doesn’t guarantee that they’ll be sent in the correct order the application is expecting – right?
A delay on the first message sent by an IoT device -> Pub/Sub causes it to be received second in line.
Pub/Sub could not detect this was actually supposed to be the first message in the order?
You’d still need DataProc to address this concern right?
Hi Ryan, I haven’t explored this new feature fully yet, but it does seem like that would be a consideration. For full control over ordering of streaming messages, I would recommend Cloud Dataflow.