Page Comparison

...

1. maintain the database of subscribers with the
   1. list of generic policy-filters (each policy-filter is the resource from the request json to /decision/v1 API) Policy Design and API Flow for Model Driven Control Loop per component - subscriber
   2. subscriber_topic for Message Router of DMaaP that uniquely identifies id should be able to globally and uniquely identify the component instance like “policies_DCAE_tca_<service-component-name>”. 
      1. Here <service-component-name> uniquely identifies the component in DCAE”
   3. subscriber_topic for Message Router of DMaaP that
      1. either uniquely identifies the component instance like “policies_DCAE_tca_<service-component-name>”. 
      2. or per whole DCAE like “policies_DCAE”
   4. option to return the policies on subscribe request
   5. option to have the matching /decision/v1 API that sends multiple policies per multiple policy-filters in a single query
2. on policy push/delete from PAP and on the insert-update of the subscriber record
   
   1. select all subscribers that match to the pushed/deleted policies by any policy-filter
   2. for each affected subscriber retrieve all the latest snapshot of policies
   3. notify each subscriber_topic separately with the latest snapshot of policies by sending the message to Message Router of DMaaP with the topic=subscriber_topic
3. there might be a need for some logic to identify the stale subscriptions by checking with the Message Router of DMaaP on the timestamps of the latest delivered/undelivered message per ach topic PDP has the subscription on

...