ThingWorx Property Change Event Flow (DataChange vs HistoricalDataLogged)

Once upon a time I witnessed large chunks of missing telemetry data after having shut down my IoT Hub Connector for awhile.

Since then my particular knack at dealing with escalated situations has provided me with the opportunity to dig deep into this subject in assistance of a number of customers.

Today in this video, I share with you a critically important aspect of how ThingWorx handles events and property updates that may be the source of missed events or data points in your ThingWorx applications.

Spolier Explanation: The high-scale ingestion across multiple threads ensures that only the freshest data will update the Thing Model and trigger events which could be tied to subscriptions. In most scenarios you only want the latest data to trigger subscriptions. When this is not the case and you need to trigger/catch all of the data (property updates), then you need to subscribe to both DataChange as well as HistoricalDataLogged events, and also ensure that the DataChange type is set to ALWAYS or ON. Best practice for cloud-scale applications is that the data/value change events should be captured and managed at the edge or close to the datas origin.