Cheers Andriy, thanks for taking so much time thinking about these concepts.

To be honest, I'm having a hard time taking your perspective probably because I'm inside a very different context, or at least haven't seen your context so far.

I'd still like to answer your questions: I'm still in the process or writing up a more generic definition of data meshes, but to me a data mesh simply means we decentralize a bunch of data work.

So: we're currently working our way through a prototypical data mesh, means we have only 3-4 domains in it so far.

It also means we don't have any data engineers dedicated to these domains, because I actually don't think that's needed. I think usually tech teams a perfectly capable of providing data in a useful form.

They also don't have a dedicated data owner. The product owner takes that role, simply adding to his list of stakeholders, with which I currently don't see a problem. On the contrary, I see that actually pretty easy to work with.

But that of course can stem from the much smaller size I'm working on here.