MDMS (Master Data Management Service)

Overview

One of the applications in the Digit core group of services aims to reduce the time spent by developers on writing codes to store and fetch master data ( primary data needed for module functionality ) which doesn’t have any business logic associated with them. Instead of writing APIs, creating tables in every different service to store and retrieve data that is seldom changed MDMS service keeps them at a single location for all modules and provides data on will with the help of no more than three lines of configuration.

Pre-requisites

Prior Knowledge of Java/J2EE.
Prior Knowledge of Spring Boot.
Prior Knowledge of REST APIs and related concepts like path parameters, headers, JSON etc.
Prior knowledge of Git.
Advanced knowledge on how to operate JSON data would be an added advantage to understand the service.

Key Functionalities

Adds master data for usage without the need to create master data APIs in every module.
Reads data from GIT directly with no dependency on any database services.

Environment Variables

Description

egov.mdms.conf.path

The default value of folder where master data files are stored

masters.config.url

The default value of the file URL which contains master-config values

Deployment Details

Deploy the latest version of Mdms-service
Add conf path for the file location
Add master config JSON path

Integration Details

Integration Scope

The MDMS service provides ease of access to master data for any service.

Integration Benefits

No time spent writing repetitive codes with no business logic.

Steps to Integration

To integrate, host of egov-mdms-service should be overwritten in helm chart
egov-mdms-service/v1/_search should be added as the search endpoint for searching master data.
Mdms client from eGov snapshots should be added as mvn entity in pom.xml for ease of access since it provides mdms request pojos.