Judge mesh honestly
Know what data mesh is, what it is not, and when it fits an organization.
Architecture Path · Operating Model · Step 4
Data Mesh Practitioner
A focused, organized path to practicing data mesh, the domain-oriented, product-first operating model behind modern enterprise data architecture. Learn the four principles in depth and apply them: domain ownership, data as a product, the self-serve platform, and federated governance.
8
Modules
40
Chapters
4
Mesh principles
Capstone
Domain data product
The journey
Eight modules, one arc
The eight modules build cumulatively toward a real capstone. Watch the work move, and the value compound, at every stage.
Each module builds the capability the next one depends on, ending in a portfolio-ready capstone.
Outcomes
What you'll be able to do
Draw domain boundaries
Define data domains and ownership that match how the business works.
Build data products
Design data products with clear contracts, quality, and discoverability.
Enable self-serve
Understand the self-serve platform that lets domains move without central bottlenecks.
Federate governance
Apply computational, federated governance that scales across domains.
Lead adoption
Sequence a realistic mesh adoption rather than a risky big-bang.
Curriculum
8 modules, 40 chapters, ending in a capstone
Eight modules of five chapters each, sequenced so the material builds cumulatively to a real, portfolio-ready capstone. Expand any module for its focus and lessons.
01 What Data Mesh Is, and Is Not
Cut through the hype and understand the problem data mesh actually solves.
- The failure modes of centralized data platforms at scale
- The four principles of data mesh, in plain terms
- Data mesh versus data lake, warehouse, and fabric
- Where data mesh fits, and where it does not
- Honest trade-offs and common misconceptions
02 Organizational Readiness
Assess whether an organization can actually operate a mesh.
- The organizational preconditions for data mesh
- Conway's law and team topologies for data
- Assessing domain maturity and data literacy
- The cultural shift from central control to federation
- Building the case for a mesh operating model
03 Domain Ownership and Boundaries
Define domains and ownership that reflect how the business really works.
- Identifying data domains from business capabilities
- Drawing domain boundaries and interfaces
- Assigning ownership, stewardship, and accountability
- Handling shared and cross-domain data
- Mapping an organization into candidate domains
04 Data as a Product: Design
Treat data as a product with users, contracts, and quality.
- The data-product mindset and its users
- Data contracts: schema, semantics, and expectations
- Product quality: reliability, freshness, and documentation
- Discoverability, addressability, and self-description
- Designing a data product for a real domain
05 Data as a Product: Delivery
Build, publish, and operate a data product end to end.
- Input, transformation, and output ports
- Versioning and evolving a data product safely
- SLOs and observability for data products
- Publishing to a catalog and onboarding consumers
- Operating and supporting a live data product
06 The Self-Serve Data Platform
Understand the platform that lets domains build without central bottlenecks.
- What the self-serve platform must provide
- Platform capabilities: storage, compute, pipelines, catalog
- Golden paths and paved roads for domain teams
- Balancing autonomy with consistency
- Evaluating a platform against domain needs
07 Federated Computational Governance
Govern a mesh so it stays interoperable and trusted at scale.
- Federated governance: what is global versus local
- Computational policies encoded in the platform
- Global standards for interoperability and security
- Balancing domain autonomy with enterprise policy
- Designing a federated governance operating model
08 Capstone: Ship a Domain Data ProductCapstone
Apply every principle to design and specify a real domain data product.
- Select a domain and define its ownership
- Specify the data product, its contract, and quality
- Define its place on the self-serve platform
- Set the federated governance rules it must follow
- Capstone: present a complete domain data-product design as a portfolio artifact
Who it's for
Built for Architects and engineers adopting a domain-oriented operating model
Data architects
Architects designing a federated, product-oriented target state.
Platform and data engineers
Engineers who will build the products and the self-serve platform.
Data product owners
Owners accountable for a domain's data products.
Engineering and data leads
Leads guiding teams through a mesh operating model.
Program formats
How you learn
Self-paced
Work through it at your own pace, with lifetime access to every module and the capstone.
Mentor-led cohort
A guided cohort with live sessions, reviews, and a peer group working the same path.
Private corporate
A closed cohort for your team, tailored to your platforms, domains, and priorities.
Portfolio-building
Every module produces an artifact; the capstone assembles them into a portfolio deliverable.
For teams
Bring it to your team
Run Data Mesh Practitioner as a private, closed cohort tailored to your platforms, domains, and priorities, as part of building the architecture capability your organization needs.
Related programs
Explore the path
FAQ
Data Mesh Practitioner - answered
Is this the old 500-chapter program?
No. This is a focused, reorganized program: eight modules, forty chapters, structured around the four principles and a real capstone, rather than an unwieldy catalog. It is designed to be completed and applied.
Who is it for?
Data architects, platform and data engineers, data product owners, and engineering leads adopting or evaluating a domain-oriented, product-first operating model.
Do I need to know data mesh already?
No, but you should be comfortable with data fundamentals. The Data Foundation program is a good precursor if you need it.
Is it vendor-specific?
No. It teaches the operating model and principles, which apply across platforms. The platform and cloud specifics live in the Cloud and Data Platforms and Serverless programs.
What is the capstone?
A complete design for a real domain data product: its contract, quality, platform placement, and governance, assembled as a portfolio artifact.
Self-paced or cohort?
Both, plus private corporate cohorts tailored to your domains.
Take the next step on the path
Enrol, enquire, or explore the full IC-to-Head of Data Architecture path.