| Table of Contents |
|---|
To fully leverage the YOUnite ecosystem, organizations need to fully understand the following areas of integration:
...
| Primary Task | Description | Interfaces Used |
| Data Integration | Generally business logic in adaptors is kept to a minimum. The sole purpose of adaptors is to both detect changes in source entities and publish them to YOUnite and to subscribe to changes published by other adaptors and process them by updating entities in the source system attached to the adaptor. | Adaptors connected to both source systems and the YOUnite message bus. |
| Governance | Scopes can be managed manually by the Data Governance Steward (DGS) and the Zone Data Stewards (ZDSs) or they can be managed programmatically by applications when well-defined events occur. For example, if a customer signs up for a new service, scope can be set so that data in a source system that already contains the customer's data is granted to a system that holds customer records for the new service. | YOUnite API |
| Notifications | Changes in data can trigger events in applications and services. YOUnite allows applications and services to register for events so that they can be notified when changes occur allowing the services and applications to start their own workflows. | YOUnite API |
| Operational Data Store | This is generally used for systems that are not connected to YOUnite through an adaptor or when the adaptor doesn't support a data domain required by the service. | YOUnite API |
YOUnite acts as an operational data store and can deliver event & change notifications
To develop adaptors see the YOUnite Adaptor Guide for Java Developers. To use the YOUnite API see the YOUnite API.
...
See YOUnite Adaptor Guide for Java Developers.
5. Receiving Data Record Changes (Data Notifications)
| Anchor | ||||
|---|---|---|---|---|
|
TODO: Move the detailed description of this to another page
...
When a YOUnite subscribed event occurs, the consumer will receive an HTTP POST request and payload to the registered URL endpoint.
6. Receiving Metadata Changes (Metadata Notifications)
YOUnite Events (TODO Anuj needs to help Mark update this)
When registering a webhook, the consumer chooses which events they want to subscribe to. The list of subscribed events can be changed at anytime. The following is list of event types that a subscriber can be notified of on a per zone -zone basis:
| Event | Event Type |
|---|---|
| A zone is created | zone_post |
| A zone is updated (including moved) | zone_update |
| A zone is deleted | zone_delete |
A data domain is created or a new version of the data domain has been created | domain_post |
A data domain has been updated | domain_update |
| A data domain has been deleted | domain_delete |
| A data record has been created for a given data domain (TBD) | dr_post |
| A data record has been updated in a given data domain (TBD) | dr_put |
| A data record has been deleted in a give data domain (TBD) | dr_delete |
...
Applications can use YOUnite as an operational data store. TODO ... point of view golden/silver request options.
See the /drs endpoint in the YOUnite API.
TODO examples