Skip to main content

Good software engineers change schemas all the time

I came across this on LinkedIn (as a screenshot from Bluesky) this morning.

Good software teams change their database schemas all the time, to add features, improve performance, fix bugs, and so on.

They don’t usually need to tell DevOps, because they use the tools provided by DevOps to make the change safely.

They don’t need to tell front-end devs, because front-end devs are using an API to access the data, not talking directly to the database, and the API rarely needs to change.

They shouldn’t need to tell data teams. The only reason they do is because data teams are consuming directly from the database, not through an interface.

That’s the problem.


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.