Skip to content

Data Engineering · Editable reference architecture

Data mesh architecture

An editable data mesh architecture reference showing Domain producer → Data product → Discovery catalog and downstream dependencies. Federate ownership without abandoning shared standards.

Open & Edit in DrawArc (Free, No Login Required)

Your changes stay in a separate draft on this browser. Download an editable project to keep a portable copy.

LinkedInTelegramReddit

Data mesh architecture diagram: Domain producer, Data product, Discovery catalog, Domain consumer and their connections
Data mesh architecture — follow the component relationships, then open the editor to adapt the design. View diagram image.

5 components · 4 connections · Open the editor to zoom, move nodes and edit source.

Architectural overview

Data mesh architecture addresses the responsibilities and boundaries shown in this reference rather than prescribing an entire production deployment. The primary flow starts at Domain producer and reaches Domain consumer through Data product, Discovery catalog. Use this view to explain which component initiates work, which component owns a decision, and where a dependency can affect the caller. Federate ownership without abandoning shared standards.

The diagram contains 5 distinct components and 4 directed relationships. A separate path connects Governance policy → Data product. These arrows describe logical interactions; they do not establish authentication, network access, atomic transactions or delivery guarantees. Label the actual protocol, payload contract and owner when adapting the drawing to your system. Keep synchronous and asynchronous boundaries explicit so that a reviewer can identify where a request ends and a later operation begins.

Before implementing this architecture, define expected load, data classification, latency budgets and recovery objectives. Give Data product a bounded dependency timeout and a documented failure response. Assign ownership to any state or external service added during implementation. Validate the decision above against your workload instead of treating the presence of a component as proof of reliability. Open the editable canvas, replace generic labels with real deployment units, and document the decisions that differ from this reference.

The real-world problem

Design or explain data mesh architecture with explicit ownership and dependency paths. Federate ownership without abandoning shared standards.

Data flow

Connections from this diagram. Branches and control signals are not a single chronological sequence.

  • Domain producer → Data product. Define the interaction contract and trace the resulting response or state change.
  • Data product → Discovery catalog. Define the interaction contract and trace the resulting response or state change.
  • Discovery catalog → Domain consumer. Define the interaction contract and trace the resulting response or state change.
  • Governance policy → Data product. Define the interaction contract and trace the resulting response or state change.

Security boundaries

  • Authenticate callers at the boundary before Data product accepts protected work; authorize the specific operation rather than trusting network placement.
  • Use separate service identities and least-privilege permissions for Data product, Discovery catalog, Domain consumer. Encrypt sensitive traffic, protect credentials and avoid placing confidential payloads in logs.
  • Validate untrusted inputs and restrict administrative/configuration endpoints separately from the main flow.

Failure handling

Data product is unavailable or slow

Response: Apply bounded timeouts and controlled backoff only where retrying is safe. Return an explicit failure or durable acceptance; do not report success before required work is committed.

Verify: Interrupt Data product in an isolated test and measure errors, recovery and any repeated side effects.

A dependency repeats or drops a request

Response: Use operation identifiers and explicit acknowledgement/reconciliation where needed. Verify idempotency before enabling retries.

Verify: Exercise the failure path with representative records and verify both the visible response and the resulting state.

An invalid or incompatible input reaches Data product

Response: Validate the input contract before effects are committed. Preserve rejected input identifiers without exposing secrets, and document a safe replay or correction procedure.

Verify: Send malformed and older-version inputs through Domain producer and verify rejection, observability and unchanged valid state.

Trade-offs and alternatives

Federate ownership without abandoning shared standards.

Benefit
Makes the ownership and interaction boundaries visible for a focused design review.
Cost
The 5 illustrated components still require contracts, monitoring and operational ownership; extra boundaries can add latency and failure modes.
Alternative
Use a simpler deployment when it meets the same requirements, or split a boundary only after measuring a specific need.

Logical boundaries versus deployment units in Data mesh architecture

Benefit
Keeps the responsibilities of Domain producer, Data product, Discovery catalog visible without requiring a separate server for each box.
Cost
A logical view does not establish isolation, independent scaling or high availability; those require a separate deployment design and operational tests.
Alternative
Co-locate components in a simpler deployment first when ownership and workload requirements permit it.

When to use this architecture

  • Explain data mesh architecture to engineers or stakeholders using a concrete visual flow.
  • Review this decision before deployment: Federate ownership without abandoning shared standards.
  • Adapt a starting diagram for your own requirements, then record and validate every changed boundary.

Key components

Domain producer
Domain producer participates in data mesh architecture. Domain producer → Data product. Define its contract, owner and access permissions in your implementation.
Data product
Data product participates in data mesh architecture. Domain producer → Data product; Data product → Discovery catalog; Governance policy → Data product. Define its contract, owner and access permissions in your implementation.
Discovery catalog
Discovery catalog participates in data mesh architecture. Data product → Discovery catalog; Discovery catalog → Domain consumer. Define its contract, owner and access permissions in your implementation.
Domain consumer
Domain consumer participates in data mesh architecture. Discovery catalog → Domain consumer. Define its contract, owner and access permissions in your implementation.
Governance policy
Governance policy participates in data mesh architecture. Governance policy → Data product. Define its contract, owner and access permissions in your implementation.

Questions about this template

What does this data mesh architecture diagram show?

It shows 5 components with the core flow Domain producer → Data product → Discovery catalog → Domain consumer. Federate ownership without abandoning shared standards.

Can I edit this diagram without signing in?

Yes. Open the template in the browser-local canvas to change nodes, connections and source. AI generation and cloud account storage require sign-in.

Is this a complete production implementation?

No. It is an editable reference. Validate the security controls, dependency behavior, capacity and recovery plan against your own requirements before implementation.

Validate your implementation

Use the relevant platform documentation to verify service limits, supported features and configuration. This diagram is an original reference rather than a reproduction of a provider deployment.