Revision for “IoT Storage Manager” created on October 2, 2015 @ 14:05:04
| Title | IoT Storage Manager |
|---|---|
| Content | The Storage Manager is a LinkSmart .net component that acts as an adapter for different storage technologies (primarily time series data). By using the Storage Manager your applications will be future-proof and you can easily change the underlying database technology. It provides support for the OPC SensorThings Data Model and API. The <a href="http://www.opengeospatial.org/projects/groups/sensorthings">OGC SensorThings API</a> provides an open and unified way to interconnect the Internet of Things devices, data, and applications over the Web. The OGC SensorThings API is an open standard, and that means it is non-proprietary, platform-independent, and perpetual royalty-free.
The Data model supported by the Storage Manager is shown below:
<a href="http://www.iotworldservices.com/wp-content/uploads/2014/12/ogcthings.png"><img src="http://www.iotworldservices.com/wp-content/uploads/2014/12/ogcthings.png" alt="ogcthings" width="1858" height="1308" class="alignnone size-full wp-image-923" /></a>
The Storage Manager consists of the following three main components:
<strong>Storage Adapter</strong>
Linksmart.NET does not specify or implement a specific storage technology. Instead, it provides a set of APIs to integrate different storage solutions depending on the application needs. Relational databases, document databases or graph stores, deployed locally or in the cloud, may be used. When the amount of time-series data - Observations - is very large, specialized databases like InfluxDb, KariosDB or OpenTSDB may be necessary. (Often, SQL Server or MongoDB is sufficient.)
<strong>Query API</strong>
A REST interface is used to query the Storage Manager. This follows the OGC SensorThings API Sensing Profile specification, a subset of OData v4. Some extensions exist to facilitate integration with other data store. The Query API is implemented using the Storage Adapter.
<strong>Receiver and Archiver</strong>
The Receiver and Archiver components listens to events from the messaging components and stores them using the Storage Adapter. Format and messaging protocol conversion is implemented by these components. Queueing of messages allows the system to adapt to bursts of events or temporarily busy storage. (Storing Observations by using HTTP POST is also possible, but this is usually not a feasible for high volumes of observation data.)
|
| Excerpt |