4 ms·
A friend is working on an IoT problem with two of your three capabilities: storage and analytics. He has voiced similar concerns. (To be fair, he gripes constan
by bostik 10y ago
A friend is working on an IoT problem with two of your three capabilities: storage and analytics. He has voiced similar concerns. (To be fair, he gripes constantly that nothing exists which would work for him, within the budgetary and timing constraints.)
His company provides sensor systems for civil engineering projects. A single large bridge can have sensor packs every 50m or so - per beam. The amount of sensor data coming in for a single municipality or region is already staggering. Vibration and stress analytics are required on a daily basis.
The final requirement, one which you didn't mention, is that this setup should be fairly low maintenance. If you need a team of rocket scientists to operate and just keep it from falling over, the cost structure will be unsustainable.
A service that provided all this in a platform with sane APIs and good BI integration should be making tons of money.
- aorloff 10y ago> budgetary and timing constraints ain't that the truth
- z3t4 10y agoInstead of storing the data and then analyzing it, make it into a stream! eg: collect | analyze | report During development or if you want to store the raw data you can split the stream. eg: collect | tee >(store) >(anotherAnalyzer) | analyze | report