Thank you for sending your enquiry! One of our team members will contact you shortly.
Thank you for sending your booking! One of our team members will contact you shortly.
Course Outline
Data Mesh Fundamentals and Principles
Module 1: Introduction and Context
- Evolution of data architecture: DW, Data Lake, and the emergence of Data Mesh
- Common issues in centralised architectures
- Guiding principles of the Data Mesh approach
Module 2: Principle 1 – Domain-owned data
- Domain-orientated organisation
- Benefits and challenges of decentralising responsibility
- Practical case studies: defining domains in a real company
Module 3: Principle 2 – Data as a product
- What is a “data product”
- Roles of the data product owner
- Best practices for designing data products
- Practical exercise: designing a data product per team
Platform, Governance, and Operational Design
Module 4: Principle 3 – Self-serve data platform
- Components of a modern data platform
- Common tools in a Data Mesh ecosystem (Kafka, dbt, Snowflake, etc.)
- Exercise: designing a self-serve platform architecture
Module 5: Principle 4 – Federated governance
- Governance in distributed environments
- Policies, standards, and automation
- Implementing data quality, security, and privacy policies
Module 6: Organisational design and cultural change
- New roles in Data Mesh: data product owner, platform team, domain teams
- How to align incentives between domains
- Cultural transformation and change management
Implementation, Tools, and Simulation
Module 7: Adoption and implementation strategies
- Roadmap for implementing Data Mesh in phases
- Criteria for selecting pilot domains
- Lessons learned from real-world implementations
Module 8: Tools, technologies, and case studies
- Data Mesh-compatible technology stack
- Implementation examples (Netflix, Zalando, etc.)
- Analysis of successes and failures
Module 9: Exam simulation and practical cases
- Revision exercises per module
- Certification-style exam simulation
- Review of results and discussion
Requirements
• Basic knowledge of data management, data architecture, or data engineering
• Familiarity with concepts such as Data Warehouse, Data Lake, ETL/ELT
• Desirable: experience in enterprise-level data projects
21 Hours
Testimonials (1)
The ability to Engauge on a 1:1 basis and ensure I had clarity and understanding on the concepts discussed.