FlowFuse
Blueprint: remote buffering
Epic
No response
Description
As a FlowFuse user running mission-critical flows on edge devices
I want to have remote buffering of data collected by my edge devices but not yet sent to a hosted instance or central server
So that in the event of an internet failure, my data is retained on the edge device until my internet connection is restored
A user collecting essential data at the edge can lose all of it if the connection is broken between the edge device and wherever that data is sent from the edge device. In some use cases, this can spoil months of work. So, we want to enable remote buffering.
The problem is that the MQTT broker is located on the server side, and not more locally available for edge devices.
This should be achievable as a Blueprint.
Acceptance Criteria
- [ ] Data collected on an edge device is not lost when a connection between edge device and server/broker/hosted instance is temporarily lost. That data is able to be retained and used at a later time.
- [ ] criteria 2
- [ ] criteria 3
- ...
Requested By
https://fathom.video/calls/433831190?timestamp=51
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
ZJ has proposed using a "store and forward" system to deliver this. Could be a very simple blueprint.
@sumitshinde-84 Please take point on this, and reach out to @Steve-Mcl for some suggestions for content to base it off of.
