Using Geo APIs in CMD

Present Reference Data Service of on-premise is based on Geo Master tables as there same MDM database. However on cloud Customer and Geography are independent MDM systems with separate DB and other other resources.

Modern Geography MDM exposes set of APIs that can provide standard list of Countries, Regions, Cities, Postal Codes. CMD can leverage the respective APIs for the data needs and validations.

CMD should ensure that this data is getting cached with standard refresh policy of 4 hours, in order to minimize the direct calls to Geo APIs. This would help with faster response, as well as avoid overloading Geo APIs that are already used by various applications.

Cache #2 is a must to have.

Cache #3 might create consistency issues if there is a difference in cache refresh schedule. Hence it would be a better idea to avoid Geo specific local cache in the respective APIs, instead all APIs should use ReferenceDataService that has its own local cache stored and uniformly catered to all.