How Fabric satisfying the 3rd principle about a data mesh

[pmscorca]

Hi,

in order to design a data mesh architecture I'd like to know how Fabric could satisty the 3rd principle that is about "Self-Serve Data Infrastructure as a Platform", simplifying data product creation and management by automating infrastructure provisioning.

Thanks

[v-cboorla-msft · Accepted solution]

Hi @pmscorca 

Thanks for using Microsoft Fabric Community.

The next component of the data mesh approach is the self-serve Data Platform. The self-serve data platform is a centralized service that serves the domains with their need for infrastructure, storage, security, access management, ETL pipelines and more. Some call this data infrastructure a platform to highlight that the self-serve platform should serve the infrastructure, i.e. all the technical components and their integrations required to build data products.
This simplicity in distributing Microsoft Fabric as a data platform as a service is one of the biggest strengths. As it is a SaaS it provides you with all the necessary infrastructure and integrations to start building your data products.
By designating a Microsoft Fabric domain for each data mesh domain, organizations effortlessly extend the self-serve capabilities to every corner of their ecosystem. This inclusivity means that every Fabric capacity holder gains unfettered access to the diverse experiences offered by Fabric, empowering them to develop their individualized data products.

For additional information please refer the below documentations:

Link 1: Self-serve data platforms - Cloud Adoption Framework | Microsoft Learn

Link 2: HOW DO YOU SET UP YOUR DATA MESH IN MICROSOFT FABRIC?

Link 3: Revolutionizing Enterprise Data Management

I hope this information helps.

Thank you.