Connectivity is at the heart of IoT solutions. Devices (things) need to be connected to a backend component where the data and functionality of the devices is leveraged to provide some higher level business value. IoT solution developers can pick from a wide array of existing (open source) technology to implement a device connectivity & management layer for the particular type of devices at hand.
I've been attending the Bosch Connected Experience IoT hackathon this week at Station Berlin. Bosch brought a lot of different devices to the event, all connected to send telemetry to Eclipse Hono. To make them more discoverable, and enable rapid prototyping I decided to expose them all to Flowhub via the MsgFlo distributed FBP runtime.
After several months of work, NoFlo 0.8 is finally out as a stable release. This release is important in that it brings the Process API for NoFlo components to general availability, paving way for the 1.x series. We introduced Process API in the 0.7 series last summer, but at that stage it wasn't deemed good enough for production use.
Embedded systems and microcontroller programs can be really hard to understand. Here are some techniques that can help. An embedded system is a computer system with a dedicated function within a larger mechanical or electrical system ...
I was looking at some of the Stack Overflow noflo questions yesterday, and there were a few related to building NoFlo for the browser. This made me realize we haven't really talked about the major change we made to browser builds recently: webpack.