References
CPS-1492 - Getting issue details... STATUS
Subscription Creation Events Handling
Assumptions
<optional, assumptions are like decision made up front ie. everyone agrees on the answer but they are important to mention>
| # | Assumption | Notes |
|---|---|---|
| 1 | Forwarded 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. |
| 2 | Forwarded 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. |
| 3 | The 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. | |
| 4 | The NCMP component should consume messages periodically from ResponseXXX topic, and create Subscription Create Outcome message. | |
| 5 | The NCMP component should publish Subscription Create Outcome message into another topic in which Client Apps consumed from. |
Issues & Decisions
| # | Issue | Notes | Decision |
|---|---|---|---|
| 1 | Do we need a analysis template? | is convention for (new) developers to guide them | Luke Gleeson and Toine Siebelink agreed we do to have consistent pages |
| 2 | This is an open issue | ||
| 3 | This is a very important (blocking issue) |
<Note. use green for closed issues, yellow for important ones if needed>
Possible Topic Names
| # | Source | Content | Topic Name | Destination |
|---|---|---|---|---|
| 1 | NCMP | Forwarded Subscription Event | TBD (cm-avc-subscription-forwarded) | DMI Plugins |
| 2 | DMI Plugins | Forwarded Subscription Event Response | TBD (cm-avc-subscription-forwarded-response) | NCMP |
| 3 | NCMP | Subscription Event Outcome | TBD (cm-avc-subscription-outcome-response) | Client Apps |