Data Extensions Mapping

Data extension is a table of the data and its fields. Data Extension helps the bank to extend product services for customizing the features as per the bank needs.

Extension Data Model

Extension tables are available as a part of the product. The relationship with the Product data entities gets created as a part of the product data model. For example, Party data model has an extension as Party_EXT as a part of the product data model. The extension data table stores extension data in the name-value format along with the parent entity relation.

Extension Support in Data Ingestion Layer

Microservice Ingester function provides facility to ingest data from the record-keeping system to inform data events. The data ingestion framework provides a configuration-based facility to map extra fields received from the record-keeping system and stores the data values in the extension data.

Schema mapping (JOLT- based) configuration needs to be created or modified to handle the mapping of the incoming extra fields and automatically gets ingested into the product extension tables. For example, the mapping of newly added fields in the AVRO DES Event Schema gets mapped to the extension fields under the appropriate entity in Microservice using jolt files.

Extension support in API layer

By default, all the Microservice product REST APIs have the extension place holder to provide or accept the extension fields as name-value pair [a,b]. Provider API of Microservice exposes these extension place holders as name-value pair without any additional development or configuration.

• GET APIs helps the user to retrieve from extension table and provide as a part of the response.
• POST and PUT APIs helps the user to accept those extension fields and persist in appropriate Extension tables.