msgflo
msgflo copied to clipboard
msgflo
Distributed Flow-Based Programming via message queues
There are situations where we have MsgFlo participants are already bound to each other. The setup should not touch those, but know that the connection exists. Example: Foreign MQTT participants...
For instance to broadcast the Flowhub live-url to connect to the system. Probably using their mDNS support, as `msgflo` broker typically runs on Linux which can have Avahi etc.
Viewing MsgFlo in Flowhub live mode, switching to edit mode: as result we have two running instances of `msgflo-register-foreign` with same role: ``` ├─702 node ./node_modules/.bin/msgflo-register-foreign participants/panel.yml --role weltenbaulab --forever=true...
Especially patterns for common usecases with good scalability properties. Should include considerations in how to implement them. ## Processing a job through different algorithms in parallel This is described a...
Another list * [Sonoff WiFi relay](https://www.itead.cc/sonoff-wifi-wireless-switch.html), ESP8266 programmable with Arduino
With MsgFlo coordinator we have two ways to have processes appear in the graph: * Started by MsgFlo coordinator itself * `--ignore`d and assumed to be running somewhere and sending...
This will make it show up nicely in Flowhub.
Now coordinator crashes on malformed discovery messages, as reported in c-base/c-flo#35 ``` May 14 03:31:26 c-flo node[3134]: Participant discovery failed: Discovery message missing .inports May 14 03:31:26 c-flo node[3134]: Error:...
Right now only works when the participants are setup due to Msgflo actions. When a participant shows up for another reason, be it coming online for first time or restarting,...
Should be documented somewhere proper, but here is good for now. Feel free to add comments! Existing for MQTT transport * [mqttwarn](https://github.com/jpmens/mqttwarn) has tons of protocol bridges, including many mobile...