Skip to content

SYSTEM Cited by 1 source

DDX (Dynamic Data eXchange) Orchestrator

DDX (Dynamic Data eXchange) is Mercedes-Benz's internal self-service meta-catalog on top of Unity Catalog + Delta Sharing. It's the control surface data-product teams interact with instead of operating shares and jobs by hand.

DDX automates:

  • Permission management — granting/revoking access via microservices and Databricks APIs.
  • Sync-Job lifecycle — creating, scheduling, and decommissioning the Delta Deep Clone jobs that materialise replicas on the consumer cloud.
  • Data sharing / replication workflows — stitching the above into end-to-end product-team-facing operations.

(Source: sources/2026-04-20-databricks-mercedes-benz-cross-cloud-data-mesh)

Why it matters (architecturally, not as a product)

A mesh without a control surface like DDX degenerates into either (a) every team operating Unity Catalog + Delta Sharing + Deep Clone directly — undifferentiated work, bugs per team — or (b) a central platform team becoming the ticket-queue bottleneck. DDX is the middle path: teams self-serve against a validated surface, and the platform retains the enforcement + observability layer.

It's the same architectural role as an internal developer platform (Backstage-style) but scoped to the data-mesh primitives instead of services.

Seen in

Last updated · 200 distilled / 1,178 read