-
Notifications
You must be signed in to change notification settings - Fork 0
Home
This Bundle defines the interface between a back-end storage and the outer world. Its purpose is to either actively fetch (as a HTTP client) or retrieve (as a web service) data from an external data source. These actions are handled each by a separate controller not implementing any data translation logic. A service called module processes the data and routes it to the storage unit.
The schema shows the two exposed interfaces, controllers and the service layer representing the actual logic to import the data to the storage.
media/architectureOverview.png
As already said the data importer is currently build upon 2 HTTP-based controllers.
The controller must not implement any logic to import data in to the storage. This has to be handled in the service injected into the controller. This is to keep the architecture and the possible options of the controller to handle different formats flexible and easy to extend.
This controller is in standby unless an incoming request triggers it into action. For more information on this controller see its detail page.
This controller is the opposite of the web-service controller. It fetches the the data actively from a source reachable via HTTP (usually a web-service). A detail description can be found on its detail page.