Transbase® Edge for Digitization, Big Data Analytics & IoT


Today's challenges

Big Data and the Internet of Things (IoT) are placing new demands on database management systems (DBMS), we fulfill as the manufacturer of Transbase® Edge. 
IoT data triggers actions on specific events in real time. If, for example, the temperature of a machine is too high, an action (switch on cooling) must be triggered in the shortest possible time after the occurrence of the event (threshold exceeded temperature).

IoT sensors permanently generate data in very large quantities. The loss of data within the measurement interval usually does not lead to significant decision changes (the cooling is switched on because of exceeding the threshold value, even if only 50 instead of 60 measured values are processed), in contrast to decisions in the classic IT environment (one share should be bought at 1.50 €  and sold at € 1.51 again).

A DBMS in the IoT environment must therefore be highly scalable, very smart, slim and secure (4S Technology). Transbase® is completely optimized in its architecture and conception to fulfill these criteria.

Thanks to its new crowd functionality, Transbase® Edge can be distributed. Results can be aggregated and consolidated across groups of edge nodes. The data can also be forwarded to analysis tools for more complex analysis. Transbase® Edge databases can also be operated as a database cluster or grids.

Transbase® Edge and Crowd

Transbase® Edge uses the new crowd function (as of v. 8.3) to control parallel database queries via any number of connected edge databases from a central instance.

While the original data is still on the edge device, the query results can be collected and aggregated by the central instance. This makes Transbase® Edge ideal as an IoT database.

For example, if a company maintains 1 million devices, each producing 1 kB of data per second, then 109 bps or 1 Gbps is required to transfer and store that data on the server. In contrast, a Transbase® Crowd query of all registered Transbase® Edge databases can be performed in seconds and their results collected.

 

The Transbase® Crowd feature also allows data to be partitioned and distributed horizontally across a pool of databases with the same database schema. Vertical partitioning of data can be accomplished by integrating the primary key into a view.

Crowd Hierarchy:

Transbase® databases can be easily integrated into a transbase® crowd hierarchy - a loosely coupled hierarchy of databases with the same or similar database schema (see figure).

 

The Hierarchy Levels
Edge Node

Every Transbase® Edge database as an 'Edge Node' has a 'higher-level database' ('Parent'), with which it can be registered. Every Transbase® Edge installation (regardless of whether as an Edge Node or Parent) has exactly the same feature set. A change within the hierarchy or constellation can therefore be carried out very easily and without programming effort.

 

Parent

Transbase® Edge takes care of the registered Edge-Nodes as a 'Parent' (intermediate node) and can send queries to these registered Edge-Nodes and collect the query results. This mechanism enables Transbase® Edge to process queries about all registered Edge-Nodes.

Each Parent can be queried directly if only the following Edge Nodes are to be part of the query. This functionality is particularly interesting for IoT environments because it only uses data that has been generated and stored in the corresponding IoT devices. They can be easily stored, analysed and processed there.

Root

Every hierarchy has a Transbase® Edge database as 'Root', which can be queried if all Edge Nodes and Parents in the hierarchy are to participate in the query. Those Edge Nodes and Parents that are not involved in the query (e.g. because they are offline) are simply not taken into account.

Different timeouts can be specified when designing the query to either get more accurate results sent from more participating Edge Nodes or to get faster results from less participating Edge Nodes.

It is also possible to specify a time interval within which an Edge Node or Parent can (re-)register. The query is then carried out with a time delay after this time interval has elapsed, e.g. include as many Edge Nodes as possible in a query result.

Transbase® Edge for IoT is always suitable when there are limitations in the collection or processing of IoT data such as
  • the bandwidth is not big enough to transfer the data
  • the server database is not fast enough to receive the data
  • there are privacy restrictions that could prevent such a transfer
  • the scalability of the overall system is not sufficient to support the growth in the number of devices

Edge Nodes and Parents can register or log out at any time, either on purpose or due to a failed database connection. The query results are therefore incomplete and can be repeated once the connection has been re-established.

Transbase® Edge & IIoT Highlights - explained

Transbase® Edge Flash Storage Support:

IoT devices typically use nonvolatile storage (flash storage) based on electrically programmable high-speed memory (see Solid State Drive = SSD). Data can be written at high speed and I / O operations can be performed very quickly. Flash memory does not require power to maintain the integrity of stored data. The data is stored in memory cells, whereby the cells with previously written data must first be deleted before new data can be written.

Flash storage is very fast, but frequent writing can significantly reduce its life. Transbase® Edge is optimized for flash storage. It detects potential memory errors for persisted data and can minimize the number of writes.

Transbase® Edge controls this through the flexible configuration of its main memory cache. Depending on the application, the cache is configured as large as necessary, minimizing physical I / O. The application gets faster and writes less often. The Transbase® cache is loaded and, depending on the size of the cache, written back to the flash storage at the latest when the database is shut down.

Transbase® Edge Log:

To ensure the stability of database changes, the Transbase® Log is permanently written to disk. This can be flexibly influenced by the IoT application.

On the one hand, the size of the log block can be configured to be larger than the size of the database block, which affects both performance and reliability. In addition, the log is written asynchronously whenever a log block is completed. As a result, there is always only one log block in memory and not on hard disk, which limits the number of lost updates in the event of a power failure.

The time and frequency of how often a log block is written can be configured.

Transbase® Edge Flash Storage Support:

IoT devices typically use nonvolatile storage (flash storage) based on electrically programmable high-speed memory (see Solid State Drive = SSD). Data can be written at high speed and I / O operations can be performed very quickly. Flash memory does not require power to maintain the integrity of stored data. The data is stored in memory cells, whereby the cells with previously written data must first be deleted before new data can be written.

Flash storage is very fast, but frequent writing can significantly reduce its life. Transbase® Edge is optimized for flash storage. It detects potential memory errors for persisted data and can minimize the number of writes.

Transbase® Edge controls this through the flexible configuration of its main memory cache. Depending on the application, the cache is configured as large as necessary, minimizing physical I / O. The application gets faster and writes less often. The Transbase® cache is loaded and, depending on the size of the cache, written back to the flash storage at the latest when the database is shut down.

Do you have questions about Transbase® Edge? We are happy to show you our system live. Schedule an appointment.​​​​​​​