Skip to main content

Leaky abstractions are ok

·1 min

All abstractions leak some details of the complexities it is trying to hide.

And that’s ok!

For example, you might abstract away the details of how a data pipeline is orchestrated to run at a time you specify.

But you still need to specify that time yourself.

And if you’re not careful, you’ll still be caught out by shifts from summer to winter time.

Trying to hide that real-world detail completely would add a lot of complexity to the platform and build in assumptions that may not be the ones the users expect.

Abstract away the details that don’t matter.

Allow those that do to leak through.


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? 😅

(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.