There are a number of core elements to the Reekoh platform designed to make integrating data from IoT and enterprise systems into business processes as agile and repeatable as possible.
Amongst those are our Plugins, which can be utilised from the Reekoh Marketplace (now numbering close to 130 and growing fast).
Gateway Plugins in particular, are a cornerstone of data workflow design in Reekoh, and act as the raw data ingestion point for nearly every integration design. Whilst we are constantly developing new types of Gateways based on device protocols and IoT systems (for example, we’re working on many industrial and utility standards at the moment), we’ve also recently updated the underlying Gateway Plugin Framework on which they’re built.
The overall goal of the new Gateway 2.0 Framework was to make these plugins more survivable, flexible and secure. Here’s what’s new:
Survivability – Reekoh gateways will now automatically store data points that cannot be relayed to the Reekoh backend due to downstream system issues. If any records are stored they will be replayed in a first-in-first-out manner before the current record. This avoids any issues with data packets being out of order once the flow of data restarts.
Storing Past Records – Reekoh gateways can now be configured to store previous data against the device as previous states. This is configurable on a per gateway basis for each device. This allows for things like statistical trend analysis, machine learning and any other functions where knowing the previous reading is essential. (Note – there is a maximum of 30 records and these are rotated on a first-in-first-out basis).
Bring your Own PKI – Reekoh gateways now support bringing your own PKI methodology. This allows customers to use their own Trusted Certificates for environments where using Self-Signed Certificates is not an option.
Flexibility – Where possible protocols have been abstracted to make it even easier to work with Reekoh. This allows customers to configure protocols in line with how manufacturer or device partners have chosen to configure the use of certain protocols.
Protocol Specific Updates:
- MQTT – Now supports wildcard topics and the ability to choose where the Device ID comes from. (JSON Body, MQTT Topic or MQTT Client ID)
- UDP – Now supports DTLS for secure version of UDP
- HTTP – Query Strings are now added as fields in the data object which allows these to be used in Converter Logic in the Reekoh pipeline
- TCP – REGEX is now supported for TCP for Devices which do not use JSON format (they may use delimited or other forms of data)
These features are rolling out now across our library of Gateway Plugins, and there’s a a large number of product feature updates coming in the second half of this year that we’re excited to bring to market.
If you’re interested in seeing Gateways 2.0 in action, you can schedule some time with our sales team.