Components¶
The Canonical Data Mesh is composed of the following charmed operators.
Component |
Role in the solution |
Charmhub |
|---|---|---|
Trino |
Federated SQL query engine; the single access layer over all connected data sources. See the Trino reference. |
|
Superset |
Self-service analytics: SQL exploration, charts, and dashboards. See the Superset reference. |
|
Ranger |
Fine-grained access policies and audit for the query layer. See the Ranger reference. |
|
DataHub |
Metadata catalog: discovery, ownership, and lineage. See the DataHub reference. |
| DataHub MCP server | Optional extension of DataHub: serves the catalog to LLM agents over the Model Context Protocol. See the MCP server reference. | datahub-mcp-k8s | | Airbyte | Connector-based data ingestion from SaaS applications, databases, files, and APIs. See the Airbyte reference. | airbyte-k8s | | Temporal | Workflow orchestration for ingestion and governance tasks. | temporal-k8s | | PostgreSQL | Relational storage for platform metadata and ingested data. | postgresql-k8s | | MinIO | S3-compatible object storage for logs, state, and large datasets. | minio | | Hive Metastore | Table metadata service for object-storage-backed Trino catalogs. | hive-metastore-k8s | | Traefik | Kubernetes ingress for the user-facing services. | traefik-k8s |
Supporting services used by individual components (for example Kafka, ZooKeeper, and OpenSearch for DataHub) are covered in the component’s own section of this documentation or in the supporting charm’s Charmhub page.