Overview

This section provides an overview on configuration based transformation, and explains the format and advantages of specification file name. Microservices can transform the input data to output data based on the configuration provided by you (developer). Henceforth, there is no need of hand-written transformation code in the respective microservices. Based on your configuration, the framework takes care of the transformation process.

• Microservices Ingester consumes, processes and sends any event to the respective microservices. The ingester then receives the event. Based on the schema, entity has to be persisted. The ingester inserts the data into database.
• The ingester internally uses jolt library to perform this operation.

Jolt Mapping Support

Microservices framework use jolt to map both Generic and Avro schema. But there are minor differences while implementing.

Format of Specification File Name

The format of specification file for both Avro and Generic ingesters is given below.

Schemaname_entityName.json - for product field (For example, PAYMENT_ORDEREvent_PaymentOrder.json)

The following are the advantages of the config-based transformation:

• It is possible to eliminate the hand-written transformation code.
• Configurations can be loaded externally, so whenever needed, the specification mapping can be changed.
• It is applicable for both sql and nosql.
• It is applicable for both Avro and Generic ingester.
• The extension and altkey mapping can be done.
• The complex type mapping and MultiRec field mapping can be done through jolt.