MDMS (Master Data Management Service)
Configure master data management service
Overview
The MDMS service 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 and creating tables in different services to store and retrieve data that is seldom changed, the MDMS service keeps them in a single location for all modules and provides data on demand 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 of how to operate JSON data would be an added advantage to understanding 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 the 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.
Integration Steps
To integrate, the host of egov-mdms-service should be overwritten in the helm chart
egov-mdms-service/v1/_searchshould 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.
Reference Docs
Doc Links
| Title |
|---|
API List
| Title |
|---|
Last updated