...
- The feature can be developed as a service that works alongside CPS to work alongside CPS core
- We can expose new endpoints for the feature, wherein the new endpoints can:
- accept two anchor names (irrespective of their schema) and generate a delta report of the JSON data stored in both the anchors
- for comparing an anchor to a payload, we can expose a second endpoint that takes one anchor and raw jSON data as input to generate the delta report or the first endpoint can be used to send the JSON as payload
- in order to to achieve this the second anchor can be defined as an optional parameter in the request
- the possibility of including the delta feature as a part of existing API's can also be explored.
- The feature will only support generating the delta for anchors within the same dataspace.
...
- the feature sounds similar to the functionality for Temporal.
- but temporal receives the full configuration of the anchor after an update, instead of the delta of two configurations.
- Update: Temporal has been disabled in CPS
Open Questions
- Can the functionality be expanded to anchors within different dataspaces?will the delta report be generated only between the latest configuration change and the reference configuration?or should the delta report be generated automatically for all the configuration changes between time T0 and Tn?this would require an automated mechanism that would trigger the delta report generation every time there is a configuration change.