@bitbonk @bitbonk good question! Indeed, the IoT model seems to be aligned with Event Sourcing, as we're listening for the events and then doing interactions. The main issue is the nature of data coming from machines and the frequency. In Event Sourcing events gather business value 1/
@bitbonk IoT data is usually raw. Also, the number of measurements and their frequency can be really high, especially for the really busy production line. Most of the event stores are not so lightweight. So they not always can be run on e.g. raspberry pi. 2/
@bitbonk Also, quite often, they have a bigger frequency than event stores can handle per second. The common pattern is to do the data ingestion. So using lightweight, but fast type of storage (e.g. key/value) or queue that will batch the events from IoT, group and change into events /3
@bitbonk This event transformation is both for performance reason but especially for making the raw events a business meaningful. I know that Postgres can be run at Raspberry PI, so maybe @marten_lib also (I didn't try that tho, probably I should 😅). .NET is also getting lightweight /4
@bitbonk @marten_lib .NET 6 should provide more optimisation and simplification. @eventstore in one of the next versions should be also possible to run on ARM, which can open more options. I haven't run .NET on Edge devices, but that's a tempting and interesting use case.
Did that help? 😅 5/5
Did that help? 😅 5/5
• • •
Missing some Tweet in this thread? You can try to
force a refresh
