Skip to main content

Why we shift left

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

What this means is we’re moving work, and responsibility for that work, closer to the source of the data.

So, instead of the source system generating raw, poor quality data, they create data that is reliable and of the right quality to be built on with confidence.

We do this for the same reasons why we don’t leave all the testing to the end of the process, carried out by a separate QA team. It’s cheaper and more effective to have these tasks done at the earliest opportunity, with short feedback cycles, by those who have the most context.

It’s a more proactive approach to the creation and management of data.

And it leads to better outcomes at reduced overall costs for the business.


Want great, practical advice on implementing data mesh, data products and data contracts?

In my weekly newsletter I share with you an original post and links to what's new and cool in the world of data mesh, data products, and data contracts.

I also include a little pun, because why not? 😅

Enter your best email here:

    (Don’t worry—I hate spam, too, and I’ll NEVER share your email address with anyone!)

    Andrew Jones
    Author
    Andrew Jones
    I build data platforms that reduce risk and drive revenue.