@tpluscode @elvis03439880 @SimenMunter@semanticarts I agree! While meta-models can be shared, you don't NEED to share them across ALL applications. Here's a visual (admittedly propaganda from my company lol) that shows how app models can be mapped to domain models to enable the real dream of composability.
@tpluscode @elvis03439880 @SimenMunter@semanticarts Agreed, and it's important to separate the model an app vendor uses from the models unique to each business.
@data_mesh_learn@khaled0ammar@SimenMunter@semanticarts All good man, my goal in producing these visuals is to drive clarity on our vision ... so the first visual is the concept of data-centricity and how the apps of the future won't 'own' data. The second visual depicts how the nodes on the first are in fact domains (with autonomy).
@data_mesh_learn@semanticarts Wasn't sure, but now I do :) And no I'm not trying to tie data mesh to data fabric, they are quite different in scope and objectives, but there is great potential for these concepts to work together for sure!
@SimenMunter@semanticarts The truth is enterprise IT didn't really have a choice. New tech like Data Fabrics and new organizational models like Data Mesh (i.e. DDD for data) are only now making this a repeatable outcome at scale.
@khaled0ammar@SimenMunter@semanticarts APIs make sense for linking (vs. copying) code to create a 'code fabric' ... using APIs for data sharing does not solve the data challenge ... data collaboration is the inevitable replacement for the data fragmentation/integration paradigm. i.e. APIs are cool for logic/code :)
@data_mesh_learn@semanticarts Yes, the vendor is cinchy and you can learn more at https://t.co/YxooUddzpD and I would love you to join us on an upcoming episode where you can rip it apart. You game?
@classonde@SeanSilcoff Hopefully it impacts only those who invested in what was predictably a dud, making more room for those able to differentiate fake news from real value.