How do we store data and access contracts?
We cannot help but observe that a lot of the content of a data contract is also part of a typical data catalog such as Microsoft Purview. Would it make sense to maintain the contract information as added attributes in Microsoft Purview? While that might look like a tempting option and hence eliminate the need for additional storage, some features such as data versioning are yet not available in Microsoft Purview. While the Microsoft Purview product team might eventually bring this feature to Microsoft Purview, you need this feature now.
Considering this situation, you have two options:
- Spread the information across different data catalogs including Microsoft Purview and maintain the missing attributes as JSON files in a separate store
- Implement a data contract as a completely separate system decoupled from the catalog
The choice between these two depends on your roadmap. If you think you will eventually switch the data...
