aboutsummaryrefslogtreecommitdiffstats
path: root/rest-services/aai-client/src/test
diff options
context:
space:
mode:
authorPiotr Jaszczyk <piotr.jaszczyk@nokia.com>2019-02-14 13:06:33 +0100
committerPiotr Jaszczyk <piotr.jaszczyk@nokia.com>2019-02-20 12:36:42 +0100
commit5020b150b594e4bb972a136156f744398eff8fd1 (patch)
tree147a2e2c4db851a13b813173526823980ce274f3 /rest-services/aai-client/src/test
parentb7399558681d2af418d0031b2ef33c28b19cfd7e (diff)
PoC of change-based configuration using MerkleTree
The goal of this MR is to check if storing application configuration fetched from CBS in Merkle Tree would be a good approach. CoS: - it should be possible to refetch configuration at some intervals - any new update should trigger changes in affected modules, ie. change of dmaap topics should trigger changes in dmaap client but not in aai client In order to satisfy this requirement a MerkleTree-based solution was proposed. The structure keeps track of hashes of each node and its subnodes. In case of a change in one branch the hash of other sibling branch will not change. Change-Id: I034be0f67d8522025a49a6ac8311b7efb8452765 Issue-ID: DCAEGEN2-884 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
Diffstat (limited to 'rest-services/aai-client/src/test')
0 files changed, 0 insertions, 0 deletions