I am using GeoEvent to process AVL data and store the data in an Geodatabase. Often, I found the data are not stored in the same order as they are received. I am curious to know how GeoEvent is maintain ordering of events when multiple events are read at a same time?
I setup a simple GeoEvent service where an input connector reads from a JSON file (about 500 JSON objects) and connected to an output connector which writes to another JSON file. My assumption is the output JSON file would match the input JSON file exactly. But, the test proves otherwise; the order of events in the output file is not the same as input.