About ELIXPEDIA Events Volume
Note that ELIXPEDIA publishes all along the day A LOT OF EVENTS (average between 10K and 20K per day).
Most of these events are because of SKU modifications due to MASS UPDATES, generally coming from external systems (SAP-ECC, WISE, APO, MINDS, MIC, COMPASS...etc.).
Obviously, these mass updates are performed on a limited list of attributes (ex. palletization , transfer prices, customs code...etc.), which probably are not relevant for all applications.
Note that the average number if LESS THAN 5 MODIFIED ATTRIBUTES PER EVENT.
RECOMMANDATION
It is absolutely key that each target application FILTERS EVENTS relying on the LIST OF MODIFIED ATTRIBUTES specified in the event payload (cf. "dataChange").
This would avoid the target application to be overwhelmed with too many events, too many API calls to invoke and too many data imports to process.
ExampleS
If the target application is only interested in only 2 attributes "A1249" and "A0216", then it must compare them with the list of modified attributes of the event.
-
Event #1 (customs code update):
dataChange": {"attributes": ["A0568"], ...}
=> TO BE SKIPPED since intersection with relevant attributes is empty
-
Event #2 (transfer prices update):
dataChange": {"attributes": ["A9369", "A9480", "A9369", "A9481", "A9965"], ...}
=> TO BE SKIPPED since intersection with relevant attributes is empty
-
Event #3 (multiple attributes update):
dataChange": {"attributes": ["A1032", "A0216", "A1025", "A9965"], ...}
=> TO BE CONSIDERED since intersection with relevant attributes is not empty