Data Mesh in LeanIX

Thanks for providing the inputs, one of the concerns while implementing Data mesh thinking in LeanIX is to be handling sub-domains impacting cross domains. Means how to handle scenarios where sub-domains shared by multiple domains?

Thanks for providing the inputs, one of the concerns while implementing Data mesh thinking in LeanIX is to be handling sub-domains impacting cross domains. Means how to handle scenarios where sub-domains shared by multiple domains?

Hi ​@ShyamBaggu 

Difficult question you have asked. In fact, it all depends on how you implemented your data mesh.
We have also started a data mesh implementation but not yet fully reflected it in leanIX yet.

As a minimum, we will create each data domain as an application. However, we wonder if we should register our data products in leanIX, since they are (or will be) also documented in our data catalog. Nothing decided yet, but an option that we might consider is an automated replication of our data products from our data catalog to leanIX.
 

Hello,

My two cents regarding synchronizing data products. For me, the most value to be had in LeanIX is visibility and managing the web of relations of the different factsheets which have their own separate master systems. 

I do not see anything wrong synchronizing data products to LeanIX as long as the information managed there is (mostly) read only and automatically synchronized. Then stakeholders can start to ask relevant questions with more information at the tip of their fingers:

• Which initiatives impact my data products?
• Are we building the right data products regarding our strategy and business capability maturity?
• Which teams depend on my data products and which ones contribute to them?

Cheers,

João

Hello,

I’m curious to know how you’ve handled this and how you’ve modelled the data mesh, specifically modelling domains and communities and synchronizing them to LeanIX.

Would you be so kind to share your experience?

Thanks,

João