Resource Synchronization Usage Scenarios
There are significant use cases that require real-time and accurate data synchronization. Consider a REST API allows users access to a collection of resources through a Virtual REST API. The goal is to keep the data on the Virtual REST API synchronized with the data of Native REST API. Types of use cases that are contemplated within the scope of the synchronization are exemplified by, but not limited to, the following scenarios:
Edit Resource Usage Scenario: You choose to reconfigure an existing Virtual REST API, and the Native REST API indicates resources that are also available in the Virtual REST API. For an exemplary illustration, see
Edit Resource Usage Scenario.
Add Resource Usage Scenario: You choose to reconfigure an existing Virtual REST API, and the Native REST API indicates resources that have been introduced since the Virtual REST API was initially created. For an exemplary illustration, see
Add Resource Usage Scenario.
Delete Resource Usage Scenario: You choose to reconfigure an existing Virtual REST API, and the Native REST API indicates resources that have been deleted since the Virtual REST API was initially created. For an exemplary illustration, see
Delete Resource Usage Scenario.
Combination Usage Scenario: You choose to reconfigure an existing Virtual REST API, and the Native REST API indicates resource metadata that has undergone various changes (modifications, additions, deletions) since the Virtual REST API was initially created. For an exemplary illustration, see
Combination of Usage Scenarios.
The outcome of each operation (edit, add, and delete) on the resource metadata is given based on a very simple instance configuration in each of the usage scenarios.
Key | Description |
Native REST API | An instance of the type "REST Service” |
Virtual REST API | An instance of the type "Virtual REST Service |