Knowledge graphs unite data mesh and data fabric architectures

Contrary to popular belief, the most meaningful developments in contemporary data architecture aren’t the rising interest in the concepts of the data mesh or the data fabric.
It’s actually the merging of these two architectural approaches into a single architecture that supports both decentralization and centralization, local data ownership and universal accessibility and top-down and bottom-up methods for creating these advantages.
The reality is that the similarities between the architectures for a data mesh and data fabric are almost greater than their differences. They’re not competing constructs for making data available across (and between) organizations; they’re actually quite complementary in achieving this objective. When properly implemented with semantic knowledge graph technologies, they fuse into a two-tiered approach for devising reusable data products that span both business domains and the enterprise.
In fact, many of the core ideas advocated by data mesh supporters are embraced by data fabric proponents.
The data mesh concept is simply a bottom-up philosophy for devolving responsibility for data to respective business units or domains while deemphasizing centralized infrastructure like data warehouses. A data fabric is a top-down methodology for devolving responsibilities for datasets closer to where the data are actually produced and is purported to utilize artificial intelligence (AI) to ‘magically’ integrate data for a centralized version of the truth.
However, both data mesh and data fabric architectures are needed. At a higher level, a data fabric can join (across an organization) the data products of a data mesh, which locally exist at a lower level. When those data assets are well described via semantic technologies, organizations can unify these architectures while reducing costs, time to value and ETL (exact, transform, load) and ELT (extract, load, transform) utilization — while also increasing their capacity to exploit data relationships.
It’s almost impossible to implement a data fabric without using data mesh ideas and techniques. A data mesh localizes data management duties to business groups instead of combining them across domains in centralized options like data lakes and data lake houses.
Data fabrics do the same thing; making one doesn’t involve centralizing everything into a single data warehouse, for example. To the contrary, it requires sourcing data from respective places, implementing Service Level Agreements (SLAs) for the data, establishing domain experts for sources, then having them formalize metadata for the data so that datasets are clean, reliable and reusable. Anyone familiar with a data mesh realizes implementing one involves those same tasks.
Data mesh supporters call these curated datasets data products. The output of a data fabric is a data product too, albeit it one at a higher level existent across an organization (instead of across a business unit).
For instance, a company may want to make SAP a source for its data fabric. The data owners for that source will make those data reusable so they’re available to the rest of the organization, but expose the data where it makes the most sense while retaining control over those assets. Data mesh adherents could (and usually do) advocate the same things for their sources.
The semantic technologies underpinning RDF knowledge graphs are primed for data mesh and data fabric architectures — and their synthesis. They’re certainly ideal for crafting data products. Semantic technologies excel at providing uniform, standards-based descriptions of data assets or products in business-friendly terminology designed for understanding and sharing them between users, systems and applications.
The crux of semantic technology is focused on sharing models of a particular domain. Experts can create these technologies so that they can be reused by anyone requiring that data product — regardless if that’s for a data mesh or data fabric.


