Low bandwidth / partially connected: message delivery priority
For scenarios with low bandwidth and connectivity issues sending messages in the FIFO order of the message cache after being offline is not working. We need a way to specify "important" messages (delivery priority) that needs to be sent before trying to send all other messages from the msg cache. Specifying different TTL values for different priorities would be necessary as well.
MP
shared this idea
2 comments
-
We acknowledge the feedback that there is room for improvement in the amount of bandwidth IoT Edge uses. This is especially important for devices on metered connections where the cost of connectivity can quickly overshadow any other business outcomes provided by an IoT solution.
We want to improve this class of scenarios for our customers; however, we don’t plan to make much progress on them in the next six months. While explicit support for limiting bandwidth usage in the IoT Edge runtime is the preferred and long term goal, Arturo Lotito has put together a nice blog post on some techniques to limit bandwidth usage by IoT device.
-
MP
commented