Chapter 5. Data Management
High values and low.
Make the data consistent.
Else, none may use it.
Generating telemetry within a device is one thing. Making that telemetry usable by other devices is a whole new ball game. Fortunately, there are ways to translate this raw data into a format that can address this challenge.
What You’ll Learn in This Chapter
To enable the CDA and GDA to “talk” with each other, we need to have a common language and data format in place. While it would be convenient to simply send a Python object to a Java application and vice versa, that’s not easily doable without using an intermediary translation first.
Data Translation and Management Concepts
With the CDA’s data collection capabilities now in place, you’re on track to eventually share that data with the GDA and leverage it to inform a better outcome than could likely be achieved if that data hadn’t been collected (and analyzed) in the first place.
In Chapters 3 and 4, you added functionality to the CDA that allowed it to collect information from simulated (or emulated) sensors and trigger simple actuation events, including the creation of three data containers to facilitate this process: SensorData, ActuatorData, and SystemPerformanceData.
With the GDA, you can use these data containers to support more advanced management ...
Get Programming the Internet of Things now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
