Term

Data Fabric

Data Fabric is an architecture pattern that uses metadata-driven automation to connect disparate data sources (lakes, warehouses, APIs, file systems) so consumers get consistent access without each team rebuilding the plumbing. Gartner popularised the term and put active metadata at its centre: the catalog observes how data is used, and that usage feeds back into integration and governance. Worth separating from Data Mesh immediately. Mesh is a socio-technical model where domain teams own their data as products. Fabric is a technical layer that unifies access via metadata. One is about who owns what, the other is about how the wires are run.
Reviewed by 7wData
Mentioned Data Mesh

Why it matters

Data Fabric tries to solve the integration problem that Data Mesh deliberately leaves to domain teams. Gartner positions the two as complementary, and on paper they are. In practice, vendors pitch them as alternatives because each side has a product to sell. My honest read: most enterprises end up with neither in pure form, just a portfolio of integration patterns labelled with whichever term sells better that quarter. The label matters less than whether the metadata layer is actually active, or a static inventory nobody updates.

Where you’ll encounter it

Three contexts. One, a Gartner-influenced procurement team writes “Data Fabric capabilities” into an RFP and you map your stack to the term. Two, a vendor positions their catalog plus integration tool as “the fabric layer” and you judge whether the active-metadata claim is real or marketing paint. Three, an internal architecture team picks between mesh and fabric as the North Star. Either works if executed seriously. The failure mode is picking both and half-implementing each.

Part of the 7wData AI Glossary. Tracking how concepts like this move in the expert conversation: daily signals at ins7ghts.com.