Aggregator

<< Click to Display Table of Contents >>

Navigation:  Technical Guide > Architecture >

Aggregator

 

The DTS Aggregator serves as the data request resolution module for aggregate data requests.

Information-icon_16px For an overview of this feature, see Aggregation.

 

It is tasked with the following responsibilities:

Registers with the Controller and implements the Aggregate definitions it receives from it.

Also registers with the Controller as a Client to make requests for specific aggregate elements.

Receives and resolves aggregate data requests routed to it by the Controller using the client connection to pass connector-specific requests onwards and provides responses directly to the requesting Clients.

Implements communication security protocols.

 

DTS Aggregators are directly linked to Projects (i.e. an Aggregator can only serve a single project's Aggregates, but will serve all of them). The Aggregator behaves both as a Producer as it receives requests and provides responses to the respective Clients, and as a Client as it generates requests for specific connectors in order to build the Aggregate records.

In a standard deployment there can be multiple Aggregator instances running inside separate containers. Depending on the scaling configuration and the current load of the system, there can also be multiple active Aggregators for each running DTS Project.

 

The Aggregator communicates with other modules as follows:

Internal Communications Bus (Redis): The Aggregator uses the ICB to receive requests routed by the Controller, to respond to Clients, to make connector-specific data requests, and to provide status reports to the Controller.