Difference between revisions of "Cross-border Subscriptions"
Jump to navigation
Jump to search
| Line 31: | Line 31: | ||
|[[Subscription and Notification Pattern|S&N]] | |[[Subscription and Notification Pattern|S&N]] | ||
|- | |- | ||
| − | | | + | |[[Notification Back-end]] |
| | | | ||
|[[Subscription and Notification Pattern|S&N]] | |[[Subscription and Notification Pattern|S&N]] | ||
|- | |- | ||
| − | + | |[[Notification Front-end]] | |
| − | |||
| − | |[[ | ||
| − | |||
| − | |||
| | | | ||
|[[Subscription and Notification Pattern|S&N]] | |[[Subscription and Notification Pattern|S&N]] | ||
|} | |} | ||
Revision as of 13:51, 3 June 2021
The Cross-border Subscription collaboration consists of one high-level component realizing the functionality needed to complete two processes in the Subscription and Notification Pattern:
- Graphic representations of the Cross-border Subscriptions application collaboration
.png)
- Subscription
- Notification
[Application Collaboration]
| Application Component | Description | Pattern(s) |
|---|---|---|
| Subscription System | S&N | |
| Required interface: Base Registry to Subscription | S&N | |
| Cross-border Event Handler | S&N | |
| Required Interface: Base Register Event stream | S&N | |
| Notification Back-end | S&N | |
| Notification Front-end | S&N |