The idea of Full-Stack Development is quite popular at the moment — building things that run both the browser and the server side of web development, usually utilizing similar languages and frameworks.
With Flow-Based Programming and the emerging Flowhub ecosystem, we can take this even further. Thanks to the FBP network protocol we can build and monitor graphs spanning multiple devices and flow-based environments.
Jon Nordby gave a Flow-Based Programming talk in FOSDEM Internet of Things track last weekend. His demo was running a FBP network comprising of three different environments that talk together. You can find the talk online.
Here are some screenshots of the different graphs.
MicroFlo running on an Arduino Microcontroller and monitoring a temperature sensor:
NoFlo running on Node.js and communicating with the Arduino over a serial port:
NoFlo running in browser and communicating with the Node.js process over WebSockets:
(click to see the full-size picture)
Taking this further
While this setup already works, as you can see the three graphs are still treated separately. The next obvious step will be to utilize the subgraph features of NoFlo UI and allow different nodes of a graph represent different runtime environments.
This way you could introspect the data passing through all the wires in a single UI window, and "zoom in" to see each individual part of the system.
Work to be done
Interoperability between them is an area we should focus on. The network protocol needs more scrutiny to ensure all scenarios are covered, and more of the FBP/dataflow systems need to integrate it.
Some steps are already being taken in this direction. After Jon's session in FOSDEM we had a nice meetup discussing better integration between MicroFlo on microcontrollers, NoFlo on browser and server, and Lionel Landwerlin's work on porting NoFlo to the GNOME desktop.
If you're interested in collaborating, please get in touch!
Photo by Forrest Oliphant.