Implementing Data Mesh

Chapter 6. Building Your First Data Product

Once we have the requirements, we are ready to build the first data product (or first data quantum), and this is what you are going to do in this chapter. You will first learn what a data product is. After that, you will see that the data contracts are going to help you immensely with your task. You will then switch to connecting the data sources to your product. You will then create the different endpoints. Finally, we’ll look at the considerations for building and packaging the data product.

Note

What is the difference between a data product and a data quantum? We wish we had a savant answer for you, but they are basically the same. The term quantum comes from the architecture world, where a quantum is the smallest deployable element that brings value. By extension, the data quantum is the smallest deployable data element that brings value. The plural of data quantum is data quanta. Although there is a slight difference between the two terms, we will continue to use data product throughout the chapters to avoid confusion.

The data products will be assembled to make a Data Mesh; you will read about this in Chapter 8.

Anatomy of a Data Product

Let’s first look at the different elements that make up a data product. This will ensure that you have a good list of the components to build.

From the outside, as suggested by Figure 6-1, a data product has many connection options.

Figure 6-1. A data product with its external interfaces