The Doppler Quarterly Fall 2016 | Page 51

Virtual Database Layer The virtual database layer is a data abstraction layer using commodity middleware that can expose custom abstract schemas and data. The data abstraction approach provides logical binding with the database at the network edge, where data is logically and physically separated and can be accessed from a single virtual schema. This reduces the number of times that the physical databases need to be changed, and places volatility into a domain. Using this approach, only the virtual database not the physical databases— need to be changed to adapt the needs of IoT applications. Finally, these abstract databases can be placed inside containers, based on the needs of the problem domain. Data Response Layer This core layer evaluates the data coming from the devices or applications and produces an automatic predefined response from the network edge. Imagine that a jet engine’s temperature reading is 50 degrees over the limit. An automatic rule is invoked: if the data point is out of bounds, the computer responds by kicking off a series of processes that are bound to the data point to bring the reading back in bounds, such as reducing the engine’s fuel flow or revolutions per minute. This occurs autonomously without the need for the centralized processes and data, although they sync at predefined points. The resulting outcome is stored in the knowledge base as a learned response, as well as any necessary changes to the approach that would make for a better resolution to that situation in the future. There are thousands of permutations just for this one data point, and an RDA can monitor and manage thousands of data points at once. In essence, this layer is a collection of data that can be mapped to different devices, applications, and data persistence layers. The layer focuses on providing automated responses and is able to learn as it processes the response. A machine-learning model is bound to the data points, thus learning through trial and error is an ongoing process. Data is stored in the abstract (see the virtual database layer), so that the physical database is updated in increments defined by the user. All data received from the sensors is processed at the network edge, though an RDA works with processes and data that exist centrally, such as in a public cloud. The core concept is that the cloud-based components and the components held near the IoT devices and sensors are logically coupled. Service/API Layer The service or API layer is the entry point into the holistic RDA. It provides access to abstract features, such as management by third-party tools or cloud-native features such as raw object storage services or resource provisioning. These APIs are managed using a service directory that includes security and governance for the use of these services and is used from within applications and devices. FALL 2016 | THE DOPPLER | 49