IoT 3.0

[architectSAP]

For many years I have been sending IoT data into central databases starting with Connect a Lego Mindstorms NXT to the HCP Internet of Things Services via a Raspberry Pi over Bluetoo..., followed by Send your Raspberry Pi sensor data to SAP Vora via Apache Kafka managed by the SAP Data Hub, and Send your Raspberry Pi sensor data to SAP Vora via Eclipse Paho MQTT managed by the SAP Data Hub.

That had advantages in that I could leverage central application logic to Display your Lego Mindstorms sensor data on a Fiori Overview Page and deploy it to the HCP Portal Fi... or Analyse your Raspberry Pi I2C sensor data with the HANA Cloud Platform, predictive services.

The architecture had been looking like this:

IoT data sent to a central instance and retrieved back from there.

With the emergence of Web 3.0 another option presented itself:

A decentralized distributed ledger holds the IoT data with the former central instance becoming an equal member.

For this blog I leverage Duino IoT that is a feature of Duino-Coin, a hybrid crypto currency.

This time, my device is an ESP32:

It mines Duino-Coin combining it with my IoT data:

Core 1 received a correct job with size of 87 bytes

Core 0 found a correct hash (2.62s)

Core 0 retrieved job feedback: GOOD, hashrate: 21.39kH/s, share #6062

Core 0 asking for a new job for user: architectSAP

AHT readings: 20.22*C, 47.76% rH

Core 0 received a correct job with size of 87 bytes

Core 1 found a correct hash (4.63s)

Core 1 retrieved job feedback: GOOD, hashrate: 21.13kH/s, share #6069

Core 1 asking for a new job for user: architectSAP

AHT readings: 20.22*C, 47.78% rH

Core 1 received a correct job with size of 87 bytes

Core 0 found a correct hash (5.54s)

As a result, my IoT data is stored with the blockchain and for example accessible through the Doino-Coin Web Wallet:

In my opinion, the potential for distributed ledgers for IoT is enormous especially also by reducing integration challenges and risks.