Data Mesh

Many data projects require investment over the long run.

It might be a transformation project, like moving towards a data mesh.

Many organisations have a data catalog as a part of their data stack. But as we move towards a more decentralised model with data mesh and data contracts it’s worth revisiting who the data catalog is for.

The whole point of data mesh is to make data in an organisation more accessible.

If you’re looking at implementing data contracts or moving towards a data mesh you will hear a lot about shifting left.

Data contracts can be used to implement a data mesh.

Consider the four principles of data mesh:

When delivering on a large project (data contracts, data mesh, or any large project) you need to realise value early and often.

There is strong alignment between the goals of data mesh and data contracts.

In fact, data mesh was one of the inspirations behind data contracts.

My post the other day on understanding the concepts, and applying them at your organisation reminded me of how I first encountered data mesh, and how I started applying some of the concepts to my organisation.

There’s a lot of great writing out there about interesting ideas like data contracts, data mesh, and much more.

I had a great panel discussion with Amy Raygada and facilitated by Jean-Georges Perrin for Data Mesh Radio.