liveBook · Manning

Data mesh

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

Data mesh is a decentralized data architecture and operating model in which domain-oriented teams own and provide data as products through shared self-service infrastructure and federated governance.

Data mesh addresses the operational cost of centralized data engineering: teams struggle with discovery, pipeline maintenance, changing regulations, access, trust, and scale while data supports decisions, risk analysis, fraud detection, and AI. section 14.0 section 14.1.3

Treat the mesh as a socio-technical operating model built from four interdependent principles:

  • Assign domain ownership so data responsibilities move closer to the relevant expertise. section 14.2
  • Provide data as a product, applying product thinking, iterative development, and ownership to its consumers and lifecycle. section 14.2
  • Offer a self-serve data platform that enables teams to build and use multiple data products. section 14.6
  • Apply federated computational governance so shared rules support trust, compliance, and interoperability across domains. section 14.6 section 14.1.3

From data quantum to mesh

A data quantum is the smallest deployable component. Its data contract governs internal and external behavior; composing multiple data quanta forms the mesh. Reusable common services can live in sidecars, while data products occupy the data product experience plane and are combined through the mesh experience plane. section 14.6 section 14.4

Approach adoption as an evolutionary change rather than a platform purchase:

  • Prepare users and leadership for cognitive load, tooling friction, and a platform build that will take longer than a few weeks. section 14.5
  • Identify users, document personas, understand current tools, and prototype with limited dependence on the infrastructure experience plane. section 14.5
  • Assemble interoperable components rather than expecting an off-the-shelf data-mesh product. section 14.5

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes
Explains four principles, data quanta, contracts, experience planes, and adoption steps, while deferring technology-specific implementation details.
Examples
Uses dashboards, reports, risk analysis, fraud detection, AI, data quanta, contracts, sidecars, and experience planes as concrete reference points.
What it assumes
Connects readily with existing Agile software engineering, domain-driven design, and data-engineering concepts.
What you can do after
Build it from scratch by defining principles, prototyping data products, composing data quanta, and evolving shared platform capabilities.
How it connects
Connects domain ownership and product thinking with Agile software engineering, domain-driven design, data contracts, and self-service data platforms.

Also explained in

Compare how 3 books explain data mesh →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.