I think that when we talk about sorting, we find that sorting should not actually be necessary. As part of that event object, there is a timestamp for what time that event got processed. As we are reading objects, we can see and compare the event timestamp for the event that took place with basically what your current version is downstream. You can use that as an ability to make sure that you are not processing delayed information off that queue.
The example would be, I edit a record 18 times in a row, right? It is that same record 18 times, it gets written into the queue. But as you read the queue, there is no guarantee that you got the newest one last. And you can look at that event timestamp to help reorganize whether you want to process this object or whether it's a historical update that just processed asynchronously, slightly out of order.
Check out the webinar on Data Extraction!
------------------------------
Mike Frasca
------------------------------
Original Message:
Sent: 08-13-2021 09:05
From: Kartik Shah
Subject: For real time consumers how can they sort the data?
Or what attribute to use for sorting the messages from the queue? #dataextraction
------------------------------
Kartik Shah
BCBSNC
------------------------------