Data Mesh & Application Mesh (MASA Architecture ‘‘Gartner’’)

I am wondering how to relate, architecturally speaking, what Gartner terms Meshed Applications & Service Architecture (MASA) and the Mesh Data Architecture referred in this post? At fist glance this seems to fit well together especially in the context of Cloud Adoption efforts offering opportunities to innovate at the Applications & Services levels. Gartner also wraps Microservices and Packaged Business Capabilities (PBCs) in what they call ‘‘Composable Organizations’’. In short each Microservice, whether containerized or not, is based on one PBC. It is a one to one relationship. The ‘‘package’’ containes the Business Capability (Value Streams, Processes, Deliverable Products, Outcomes, Reach and measurable results — whatever the busines capability needs — with the Technical/Technology Capability required to make the Microservice Application run. Democratization of IT allows for the creation of these Microservices by Business & IT resources agile teams to co-create these solutions and maintain them together. Given Data (and Security) are too often missing in action (MIA) in these architecture, the data mesh content shared seems a perfect fit. Would you have examples of how these could be used together ultimately enable the ‘‘Composable Organization’’ — sort of a compelling Vision of the Organizational struture based on IT progress and maturity. Very compelling indeed, at least to me.