Data Mesh 101: Data Ownership by Domain

This serious is gold. Although it’s obvious that it is to promote confluent it is very accurate in the real world. What caught me attention was him using the right words like instead of saying „data warehouse does not work“ (what is very wrong) saying „on a non-trivial scale) I’ve been working in the analytics department for many years so I feel like getting bullshitted by many self claimed experts talking about data mesh/fabric lately

Look at this project stratos it's a decentralised approach of a data mesh.. 😁😁.. thank yu for your videos.. it's amazing .

The teams(domains) that manager operational system(Order management, CRM) would not consider making their data available as a clean, governed product as "added value" to the company since they would already be pushing Their data to a datalake, of some sort, and someone else(another domain) cleans and governs it. Since the raw(est) data an organization has is the data that comes from operations systems (Order management, CRM) for a transition to datamesh to work these team would have to consider the work needed to clean, govern and publish their datasets as adding value to the company. In my experience this is why most of these project stall of fail. What change management strategy would you recommend to improve the success rate of such projects? Can you elaborate on what "incentives" you have seen work?

Thanks alot! Does this mean that each local domain has its own data store (data base)? Or I can use this Kafka/Confluent to read data from third party so that either Alice or Joe can consume and use the data locally as they desire? Thanks