data-mesh-governance

# Data Mesh Architecture and Federated Data Governance This skill establishes the architectural and operational principles for transitioning from centralized monolithic data lakes to a decentralized, domain-oriented approach (**Data Mesh**), with automated governance and formal data contracts. --- ## 🏛️ 1. The 4 Foundational Data Mesh Principles 1. **Domain Ownership**: Business/engineering teams that own the operational domain are responsible for its analytical data. 2. **Data as a Product (DaaP)**: Analytical data has identified consumers, quality SLAs/SLOs, documentation, and formal contracts. 3. **Self-Serve Data Platform**: Domain-agnostic infrastructure that abstracts away the complexity of provisioning pipelines, storage, and access. 4. **Federated Computational Governance**: Security, privacy (LGPD/GDPR), compliance, and audit policies applied automatically as code (*Policy as Code*). --- ## 📜 2. Structure of a Data Contract (OpenDataContract Specification) ```yaml version: 1.0.0 dataset: orders_completed domain: checkout_financial owner: team-checkout@empresa.com status: active sla: freshness: 5m availability: 99.9% schema: - name: order_id type: string description: "UUID of the approved transaction" required: true pii: false - name: customer_tax_id type: string description: "CPF/Tax ID of the buyer" required: true pii: true classification: restricted - name: total_amount_cents type: integer description: "Amount in cents of the local currency" required: true ```