msgflo
msgflo copied to clipboard
msgflo
Distributed Flow-Based Programming via message queues
https://github.com/octoblu/meshblu http://www.wired.com/2014/02/skynet/
http://www.thedotpost.com/2015/06/salvatore-sanfilippo-introducing-disque https://www.npmjs.com/package/disque.js
http://googlecloudplatform.blogspot.de/2015/03/using-Google-Cloud-pubsub-to-Connect-applications-and-data-streams.html https://www.npmjs.com/package/cloud-pubsub
https://github.com/ipfs/notes/issues/64 https://news.ycombinator.com/item?id=12721316
Should persist the information to disk, so that it can be recovered. This especially useful as a stop-gap until we enforce periodic heartbeats (#30). But also afterwards, as the heartbeats...
msgflo-setup does things in this order: * Start participants, wait for STDOUT (#92) * Subscribe to `fbp` queue and wait for discovery messages However, noflo-runtime-msgflo currently sends the discovery message...
The participant starting code in msgflo-setup calls its callback on: * Receiving to STDOUT * Spawn error * Exit When calling msgflo-setup-foreign, none of these three happens currently.
That way the messages will not crop up in an unused queue when there is no coordinator, and there can be multiple consumers of the messages instead of just one....
Split out from #30 The participant itself should indicate how often it intends to send discovery messages. This enables them to for instance optimize for battery usage (maybe a microcontroller...
https://micropython.org is a Python implementation for bare-metal microcontrollers, including some with WiFi support like ESP8266. It has a MQTT library included for these devices, https://github.com/micropython/micropython-lib/tree/master/umqtt.simple So it should be usable...