Details

    • Type: Improvement
    • Status: Deferred
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: TRS
    • Labels:
      None
    • Proposal:
      Hide

      We should discuss the use of push-based mechanisms so that data providers can publish a message that is received by link index consumer so that it can update its data quickly after the data change is made. If a consumer relies solely on a push-based design, then we should discuss requirements for guaranteed delivery so that stale indexed data is not left in the consumer for long periods.

      MQTT is an obvious candidate technology for a publish and subscribe approach. While MQTT brokers typically offer guaranteed delivery (QOS 1 or 2), that is insufficient. Data providers need to ensure that committed data changes also guarantee publication of an event is successfully received by the MQTT broker. MQQT client libraries such as Paho do not currently provide a solution for this client delivery gauantee requirement.

      Show
      We should discuss the use of push-based mechanisms so that data providers can publish a message that is received by link index consumer so that it can update its data quickly after the data change is made. If a consumer relies solely on a push-based design, then we should discuss requirements for guaranteed delivery so that stale indexed data is not left in the consumer for long periods. MQTT is an obvious candidate technology for a publish and subscribe approach. While MQTT brokers typically offer guaranteed delivery (QOS 1 or 2), that is insufficient. Data providers need to ensure that committed data changes also guarantee publication of an event is successfully received by the MQTT broker. MQQT client libraries such as Paho do not currently provide a solution for this client delivery gauantee requirement.

      Description

      The current TRS design is based on a pull model in which a consumer has to keep polling the TRS to determine whether there are TRS events for tracked resources of interest. There is a tradeoff between the overhead of frequent polling and the latency in which indexed resources may have stale data after the data provider has applied changes and published events. This makes it difficult for the current design to satisfy requirements for a low-latency solution without the overhead of frequent and continuous polling.

        Attachments

          Activity

            People

            • Assignee:
              jamsden James Amsden
              Reporter:
              DavidHoney David Honey
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: