Source
book_cube #Data
A compact review of the book with structure across three parts and nine chapters.
Data Mesh in Action
Authors: Jacek Majchrzak, Tamás Balnóyan, Zhamak Dehghani
Publisher: Manning Publications, 2023
Length: 312 pages
A practical guide to adopting data mesh: domain ownership, data as a product, federated computational governance, self-serve platforms, and an MVP in one month.
OriginalWhy this book is practical
The book provides a pragmatic Data Mesh adoption path: validate value with a narrow MVP first, then scale through domain ownership, data product thinking, and automated federated governance.
For data teams
How to reduce central backlog pressure and improve time-to-data for business consumers.
For platform engineers
How to build a self-serve layer that actually enables domains instead of re-centralizing ownership.
For architects and leads
How to balance local team speed with shared quality, security, and compliance requirements.
Book structure: 3 parts, 9 chapters
Part 1: Foundations
What Data Mesh is, when it fits, and how to ship an MVP in one month.
- 1. The What and Why of the Data Mesh
- 2. Is a Data Mesh Right for You?
- 3. Kickstart Your Data Mesh MVP in a Month
Part 2: The Four Principles in Practice
A practical walkthrough of the four core principles in production conditions.
- 4. Domain Ownership
- 5. Data as a Product
- 6. Federated Computational Governance
- 7. The Self-Serve Data Platform
Part 3: Infrastructure and Technical Architecture
Platform comparison and architecture design under functional and non-functional requirements.
- 8. Comparing Self-Serve Data Platforms
- 9. Solution Architecture Design
The four Data Mesh principles in practice
Domain Ownership
Data accountability moves to domain teams that are closest to data creation and business context.
Data as a Product
Data is treated as a first-class product with clear APIs, metadata, quality standards, and consumer support.
Federated Computational Governance
Central policies and compliance are automated in a federated setup without removing local team autonomy.
Self-Serve Data Platform
A self-serve platform enables domain teams to publish, operate, and evolve data products independently.
One-month Data Mesh MVP
- Align MVP goals and success metrics for one priority domain.
- Pick a limited data scope with clear consumers and obvious pain from centralized ownership.
- Assign a domain owner team, define a minimal data product contract, and set quality gates.
- Build a thin self-serve path (catalog, access, monitoring, basic policy enforcement).
- Run a stakeholder demo and agree on the next-domain rollout plan.