Enterprise Metadata Management System  ·  View 17 of 22  ·  Operations

Delivery and Extensibility

How a new connector, a new asset type and a platform change each reach production.

Editable source SVG draw.io All views
Source
Source
Platform services
monorepo
Platform services...
Connector plugins
versioned separately
Connector plugins...
Aspect schemas
the metadata model
Aspect schemas...
Build & test
Build & test
Unit + contract tests
Unit + contract tests
Connector conformance
golden payloads
Connector conformance...
Schema compatible?
backward only
Schema compatible?...
Gate
Gate
SAST · SCA · secrets
SAST · SCA · secrets
Migration dry run
on prod snapshot
Migration dry run...
Model change board
new asset types only
Model change board...
Blocked
breaking change
Blocked...
Deploy
Deploy
Dev
synthetic estate
Dev...
Staging
prod metadata subset
Staging...
Production
blue/green
Production...
Verify
Verify
Smoke harvest
one asset per class
Smoke harvest...
Projection lag check
under 60 s
Projection lag check...
Rollback
one release back
Rollback...
breaking
breaking
on failure
on failure
Delivery Pipeline and Extensibility
Delivery Pipeline and Extensibility
Application we own
Application we own
Decision point
Decision point
Security / platform
Security / platform
Risk / gap
Risk / gap
failure / alternate
failure / alternate
A new source type ships as a plugin and a new metadata attribute ships as an aspect schema. Neither requires a core platform release.
A new source type ships as a plugin and a new metadata attribute ships as an aspect schema. Neither requires a core platform release.
v 1.0 · owner Platform Engineering · date 2026-08
v 1.0 · owner Platform Engineering · date 2026-08
Text is not SVG - cannot display

Decisions

  • Three independently versioned artefacts: platform services, connector plugins and aspect schemas. A new source or a new attribute does not need a platform release.
  • Aspect schema changes must be backward compatible. A breaking change is blocked in the pipeline, not discussed after deployment.
  • New asset types go to a model change board. The canonical model is the shared contract; letting each team extend it privately recreates the silo.

Gates

  • Connector conformance tests run against recorded golden payloads, so a source-API change is caught in CI rather than in production ingestion.
  • Migrations are rehearsed against a production snapshot before they run against production.
  • Post-deploy smoke harvest covers one asset per source class; projection lag above 60 seconds triggers rollback.

Assumption

  • Staging holds a subset of production metadata with restricted assets excluded, refreshed weekly. Testing a catalog against synthetic metadata only proves the code compiles.