3 ms·
Nice work with the open pipe project. Looks perfect for DIY sensor/telemetry projects. If you are looking to monetize connectivity services, you certainly will
by roymurdock 10y ago
Nice work with the open pipe project. Looks perfect for DIY sensor/telemetry projects.
If you are looking to monetize connectivity services, you certainly will need a bi-directional architecture to push values back to end nodes, and compute resources available at the gateway for data filtering, preprocessing, and security.
But these are tasks that AWS IoT, Azure IoT, and GCP IoT are currently tackling with a lot of resources. So it would be hard to compete at that level.
- ausjke 10y agolibwebsockets is better suited comparing to the pub/sub model for that? two-way communication is pretty tricky(NAT-traversal etc) sometimes, I am still opt for the old but reliable polling mode for most of IoT nodes.
- staticvar 10y agoThanks. While our examples are usually "pull from some device and push to a database", with farmOS we experimented with "pull from a database and push to a device". In this way, pipes are used to transfer state of a device two ways. This depends on a database UI giving users the option to modify the state of something, something that IoT databases like Phant (http://data.sparkfun.com http://data.sparkfun.com) and Adafruit IO (http://io.adafruit.com http://io.adafruit.com) don't currently support.