Data Mesh

Part III. How to Design the Data Mesh Architecture

The supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a simple datum of experience.

Albert Einstein

Up to this point in the book, I’ve left the technical design of a data mesh architecture to your imagination. This was necessary. We first needed to share a common understanding of what data mesh is (Part I) and agree on why we need to shift toward it (Part II). Now it’s time to model an architecture that enables a technical implementation of the data mesh.

The Scope

At the time of this writing, data mesh is in its early years of development. We still have a long way to go to learn about its optimal design. Hence, the scope of this part is respectful of the fact that data mesh design and implementation will continue to evolve. Nevertheless, we have to start somewhere. So I’ve decided to dedicate this chapter to the important stuff¹ that matters today, aspects of architecture that I think will continue to last and influence the development of future implementations.

What is the important stuff?

It’s important to have a shared understanding of logical architecture. In Chapter 9, “The Logical Architecture”, I will define the main logical components of data mesh architecture such as domains, data product as an architecture quantum, and multiple planes of data platform and how they interact with each other.

Chapter 10, “The ...