Forum Discussion

pmscorca's avatar
pmscorca
Icon for Post Prodigy rankPost Prodigy
2 years ago
Solved

How implementing a data product/data mesh in Microsoft Fabric

Hi, I need to implement some data products (see data mesh architecture) using Fabric and I'd like to have some suggests. For example, could a workspace represent a domain (1-to-1 relationship)? To ...
data engineering
data warehouse
one lake
  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi pmscorca 

    Several of Microsoft Fabric's features directly support the data product concept:

    • Unified Data Platform: Fabric brings together various data tools and technologies into a single platform. This simplifies data integration, management, and access for data professionals, allowing them to focus on building and refining data products .

    • Data Integration and Ingestion: Fabric excels at seamlessly integrating data from disparate sources. This is crucial for data products, which often rely on combining data from various internal and external sources to generate insights .

    • Data Governance and Security: Fabric offers robust security features and centralized governance policies. This ensures the data used in data products is secure, reliable, and adheres to organizational compliance standards.

    • Collaboration and Sharing: Fabric empowers teams to collaborate and share data easily. This fosters a collaborative environment for developing and refining data products.

    • Empowering Business Users: Fabric integrates with Microsoft 365, allowing business users to access and analyze data directly within their familiar applications. This broadens the potential user base for data products.

    In summary, Microsoft Fabric's features streamline data access, management, security, and collaboration – all essential aspects of bringing data products to life.

Anonymous's avatar
Anonymous
Not applicable
2 years ago

Hi pmscorca 
Thanks for using Fabric Community.

Implementing data products using Fabric and aligning them with a data mesh architecture can be quite effective. Here are some suggestions:

Workspace as a Domain:
Yes, in Fabric, a workspace can indeed represent a domain, establishing a 1-to-1 relationship. This allows for organizing and governing data within specific business domains, such as marketing, sales, or human resources.
Domains - Microsoft Fabric | Microsoft Learn

Data Quality Implementation:
 For implementing data quality within these domains, you can leverage Fabric’s features that support federated governance. This means governance can be delegated to domain-level control, allowing each domain to define its own rules and restrictions according to specific business needs.

Getting Started:
To get started with domains in Fabric, you can create new domains and subdomains through the Admin portal, assign domain admins, and associate workspaces with domains.

For more information please refer to these links:
Easily implement data mesh architecture with domains in Fabric | Microsoft Fabric Blog | Microsoft Fabric
Domains - Microsoft Fabric | Microsoft Learn
Establishing Data Mesh architectural pattern with Domains and OneLake on Microsoft Fabric - Microsoft Community Hub

Hope this helps. Please let me know if you have any further questions.