Data Product in a Nutshell
A big-picture layout shaped by TOGAF’s domains
Intro
A Data product slowly becomes a next-generation version of the Data Mart. This might sound controversial, but this is quite accurate when considering the building blocks of data analytics storage nowadays.
To build a simple and robust decentralized architecture, you need to understand its key characteristics, which make that architecture succeed.
This article aims to outline the key pillars of data product design as a part of Data Mesh architecture and provide guidance on structuring it clearly and precisely.
Let’s examine the elements at both levels:
- External view: The context in which a Data Product exists.
- Internal view: Building blocks of the Data Product itself.
External View
Please review the metamodel for the Data product context on the diagram below.
TOGAF’s architectural domains — Business, Data, Application, and Technology — are used to set up the layout. Let’s examine quickly the structural components on the diagram.
