Versions Compared

Old Version 12

changes.mady.by.user Rajesh kumar

Saved on

compared with

New Version 13

changes.mady.by.user Rajesh kumar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 It is important to control the delta notification for better performance. we need to decide on below options to control delta notification.

OptionPros and Cons Decision
Send delta notification for the update operation when update request contains optional query parameter to receive notification. 

Pros:

  1. Dynamically control notification and per request level. 

Cons: 

  1. there could be issue with access control

Configure dataspace/anchor in yaml file to allow delta notification.

Pros:

  1. Only allowed dataspace/anchor's delta update will be sent in notification

Cons:

  1. Not practical because we can't control the notification dynamically.  

while creating dataspace/anchor, configure to send delta notification. 

Pros: 

  1. control the notification dynamically.

Cons:

  1. Need to persist notification information in DB. 
We decided to try this approach. detailed implementation provided below. 


Implementation of controlling delta notification 

...

delta notification can be disabled for an anchor in anchor update API. 

additional header in create/update anchor request

Parameter Description
Set-Detla-Notificationtrue/false.

Additional table to persist delta notification 

Table Name: AnchorForDeltaNotification

Fieldtype
Anchor IdInteger

Implementation details

  1. For data nodes update operation, generate delta report by comparing previous and current configuration after successful update. 
  2.  Process data update delta event and send notification as described in event schema above.