A system architecture for augmentation and routing of calls requesting data, the system architecture leveraging calling source data, vendor data and internal data, the system architecture comprising:
- a first I/O platform for:
- receiving a call from a calling source, the call including a first data request and a transaction indicator, wherein the call is received from an IP address and the transaction indicator specifies how current a piece of data must be to satisfy the first data request;
- and
- pushing the IP address to a calling sources database;
- the calling sources database for:
- retrieving a calling source indicator and a second data type associated with the IP address;
- and
- transmitting the calling source indicator and the second data type to the first I/O platform;
- the first I/O platform further configured to:
- augment the call to include a second data request and tagging the call with the calling source indicator, wherein the second data request requests the second data type;
- and
- after the augmenting, transmit the call to a processing engine;
- the processing engine for receiving the call from the first I/O platform and, in response to receiving the call:
- transmitting the first data request, the second data request and the transaction indicator to an intermediate cache;
- in response to receiving, from the intermediate cache, data for fulfilling the first data request, the second data request and the transaction indicator, populating the call with the received data and transmitting the call to the first I/O platform for routing to the calling source;
- and
- in response to receiving a null result from the intermediate cache, transmitting the call to a second I/O platform;
- the second I/O platform for:
- receiving the call from the processing engine;
- in response to receipt of the call from the processing engine, pushing the IP address, the first data request, the second data request and the transaction indicator to a vendor source broker engine;
- receiving, from the vendor source broker engine, a data source and a call format;
- formatting the call to conform to the call format;
- after the formatting, pushing the call to the data source;
- receiving from the data source a response to the call, the response including first data and second data;
- transmitting to the vendor source broker engine performance metrics associated with the response received from the data source;
- and
- transmitting the response, in parallel, to both a vendor data intelligence engine and the processing engine;
- the vendor data intelligence engine for:
- receiving the response from the second I/O platform;
- and
- executing a determination whether to store, in the intermediate cache, one or both of the first data and the second data;
- the processing engine for:
- receiving the response from the second I/O platform and extracting from the response the first data and the second data;
- pushing to an internal repository database the calling source, the first data and the second data;
- receiving, from the internal repository database, a third data field loaded with third data;
- processing the first data, the second data and the third data to output a binary response, the binary response not including the first data, the second data or the third data;
- and
- transmitting the binary response to the first I/O platform;
- and
- the first I/O platform for routing the binary response to the calling source.