Enterprise Metadata Management System  ·  View 05 of 22  ·  Structure

Integration Architecture

Every interface in and out, and the rule that keeps the platform from becoming another silo.

Editable source SVG draw.io All views
Metadata producers — inbound
Metadata producers — inbound
Snowflake / BigQuery
JDBC · ACCESS_HISTORY
Snowflake / BigQuery...
Databricks Unity Catalog
REST · system tables
Databricks Unity Catalog...
dbt / Airflow / Spark
OpenLineage
dbt / Airflow / Spark...
Power BI / Tableau
REST · usage API
Power BI / Tableau...
Kafka Schema Registry
subjects
Kafka Schema Registry...
SAP / Salesforce
metadata API
SAP / Salesforce...
Enterprise Metadata Platform
Enterprise Metadata Platform
Metadata Hub
canonical model · APIs
Metadata Hub...
Connector Framework
pluggable SDK
Connector Framework...
Metadata Event Bus
Kafka
Metadata Event Bus...
GraphQL · REST · Events
GraphQL · REST · Events
Metadata consumers — outbound
Metadata consumers — outbound
Policy Enforcement
masking · row filters
Policy Enforcement...
Quality Platform
Soda · GX
Quality Platform...
ITSM & Incident
ServiceNow
ITSM & Incident...
Notebooks & IDEs
inline lookup
Notebooks & IDEs...
Enterprise Search
M365 · Glean
Enterprise Search...
Metadata Exchange
OpenLineage · CSV
Metadata Exchange...
schema · query log
schema · query log
schema · lineage
schema · lineage
run events
run events
reports · usage
reports · usage
event schemas
event schemas
objects · fields
objects · fields
labels · tags
labels · tags
asset scope
asset scope
impact tickets
impact tickets
GraphQL
GraphQL
asset index
asset index
open export
open export
Integration Architecture — Producers, Hub, Consumers
Integration Architecture — Producers, Hub, Consumers
External / third party
External / third party
Application we own
Application we own
Interface / broker
Interface / broker
Queue / topic
Queue / topic
batch
batch
event / async
event / async
synchronous
synchronous
Every inbound connector is read-only. Outbound writes are limited to tags, labels and tickets — never to source data.
Every inbound connector is read-only. Outbound writes are limited to tags, labels and tickets — never to source data.
v 1.0 · owner Integration Architecture · date 2026-08
v 1.0 · owner Integration Architecture · date 2026-08
Text is not SVG - cannot display

Decisions

  • Every inbound connector is read-only and scoped to catalog and log views. The platform never holds write credentials to a source.
  • Outbound writes are limited to tags, labels and tickets. The platform tells other systems what is true; it never changes their data.
  • Standard formats where they exist: OpenLineage for run lineage, the source's own metadata API otherwise. No proprietary agent on a database host.

The anti-silo test

  • Anything the catalog knows is retrievable through GraphQL, exportable in bulk, and emitted as an event. If a team can only get an answer by opening the UI, the integration is incomplete.
  • Enterprise search indexes asset profiles, so discovery does not require knowing the catalog exists.

Risks

  • Source API rate limits are the binding constraint on harvest freshness, not platform throughput (view 22).
  • Bidirectional quality integration means a change in the DQ platform's result schema breaks ingestion. Contract tests against golden payloads are in the pipeline (view 17).