In this final chapter, we will walk through the ideas proposed in the previous chapters by looking at an example of a simple streaming data mesh. We will go through the experience of building streaming data products using data domains (a collection of values that are related to one subject area) as an example.
Figure 10-1 shows the streaming data mesh example that we will use in this chapter. The control plane in this example does not have all the components that appear in the latter part of Chapter 7. It includes only the necessary components to build, publish, and share streaming data products across domains:
A schema registry
Data lineage
Airflow for ETL workflow execution
A data management plane that includes a CLI for administration
Components within the data domain that stream data into the management plane
In Figure 10-1, we have taken out the repository that holds libraries like Kafka connectors or UDFs since we will not be showing this use case. We’ve also removed the Confluent Schema Registry, replacing it with the schema registry that comes with Apicurio. The Confluent Schema Registry will come into play within the domains that we will cover in a later section. Lastly, we have omitted Prometheus and Grafana. This reduces the number of services and the resources needed to run them on the local computer.
Figure 10-1. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month, and much more.
