Difference between revisions of "Cross-border Subscriptions"
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
|- | |- | ||
|[[Subscription System]] | |[[Subscription System]] | ||
| − | |Application component managing the entire life cycle of subscriptions. | + | |Application component managing the entire life cycle of subscriptions, ie creation and maintaining subscriptions. |
The component provides an interface for the base registry. | The component provides an interface for the base registry. | ||
Revision as of 09:54, 4 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 Component | Description | Pattern(s) |
|---|---|---|
| Subscription System | Application component managing the entire life cycle of subscriptions, ie creation and maintaining subscriptions.
The component provides an interface for the base registry. |
S&N |
| Cross-border Event Handler | Application component handling the cross-border events. It filters all national events for relevant cross-border events and takes care of preparing a notification message and compiling a subscribers list.
The component provides an interface for the base registry. |
S&N |
| Notification Back-end | Application component serving the front-end | S&N |
| Notification Front-end | Application component providing the UI for civil servants in order to dispatch events and consult logging information for trouble shooting. | S&N |