Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 10 Next »

References

CPS-1492 - Getting issue details... STATUS


Subscription Creation Events Handling

Assumptions

#AssumptionNotes
1Forwarded Subscription Event communicates asynchronously.  (NCMP to DMI Plugins)  Thus, it is not required to wait for a single request to be responded. For example, NCMP has not to wait a response when Forwarded Subscription Event has been published into a topic, e.g. RequestXXX.
2Forwarded Subscription Event Responses communicates asynchronously.  (DMI Plugins to NCMP) 

It is the same as above note. The Forwarded Subscription Event Responses published into a different topic, e.g. ResponseXXX.

3The NCMP component need to keep the Request ID that is belong to each Kafka message and the timestamp when the message is published into RequestXXX topic. 
4The NCMP component should consume messages periodically from ResponseXXX topic, and create Subscription Create Outcome message. 
5The NCMP component should publish Subscription Create Outcome message into another topic in which Client Apps consumed from.

Issues & Decisions

#IssueNotes Decision
1Possible Topic Names (TBD)

Toine Siebelink , Luke Gleeson (Unlicensed) , Sourabh Sourabh  and Lee Anjella Macabuhay  

2Possible 'timeframe' period to consume Forwarded Subscription Create Event ResponsesTBD for timeframe

Possible Topic Names

#SourceContentTopic NameDestination
1NCMPForwarded Subscription EventTBD (cm-avc-subscription-forwarded)DMI Plugins
2DMI PluginsForwarded Subscription Event ResponseTBD (cm-avc-subscription-forwarded-response)NCMP
3NCMPSubscription Event OutcomeTBD (cm-avc-subscription-outcome-response)Client Apps

Implementation Details

  1. The NCMP component could utilize a Hash Map to store request_id and timestamp the time that message is published into the topic mentioned in #1 → Possible Topic Names
  2. In order to calculate the Subscription Create Outcome Message, the NCMP component should consume response messages from the topic mentioned in #2 → Possible Topic Names
    The NCMP component should consume messages as per the timeframe periods, and compare request ids with the ones that already kept in that Hash Map at step 1.
  3. If the incoming request id is found in the Hash Map, the total time elapsed could be calculated via timestamp (responses read) minus timestamp from Hash Map (for related request id).
  4. The NCMP can populate Subscription Event Outcome report, and publish it to the topic mentioned in #3 → Possible Topic Names 

Testing Details


Ref: Component Diagram


  • No labels