🏷️Domain-Oriented Data

NEW

Also known as: Domain Data, Domain-Aligned Data

Data organized around business domains to align semantics, ownership, and accountability with domain teams.

DESCRIPTION

Domain-oriented data structures model information around bounded business contexts. They reflect domain language, processes, and metrics, enabling clarity and reuse. Ownership, SLAs, and governance align with domain teams. Inter-domain contracts, shared semantics, and standard interfaces enable interoperability. This approach supports data mesh and product thinking. It reduces ambiguity by avoiding one-size-fits-all canonical models. Adoption requires strong glossary management and collaboration across domains. Domain orientation improves discoverability, trust, and change management.

ALTERNATIVE DEFINITIONS

Martin Fowler

A bounded context is a central pattern in domain-driven design that partitions a larger system into coherent domains.

Highlights domain partitioning for coherent semantics.

Source

Wikipedia

Domain-driven design is an approach to software development that centers the modeling of software to match a domain according to input from domain experts.

Connects domain modeling to expert knowledge and language.

Source

Martin Fowler (Zhamak Dehghani)

Data mesh applies domain-driven design to data, aligning ownership and models with business domains.

Applies DDD concepts specifically to data modeling and ownership.

Source

RELATED TERMS

Decentralized Data Architecture Data Domains Domain-Driven Design Data Product Semantic & Knowledge Modeling Knowledge Representation

COMPETING TERMS

Enterprise-wide Canonical Data Model

RELATIONS

• Broader: Data

KNOWLEDGE AREAS

Data Architecture Domain & Business Context Semantic & Knowledge Modeling Data Management Data Modeling

TARGET AUDIENCE

Data Architect Data Modeler Data Steward Information Analyst Chief Data Officer Data Strategy Consultant

EXTERNAL SOURCES

• Wikipedia - Domain-driven design
• Martin Fowler - Bounded context guidance
• Martin Fowler - Data mesh principles
• Thoughtworks - Technique overview on domains

TOP QUESTIONS

What is Domain-Oriented Data?

It models and governs data around bounded business contexts, aligning semantics and ownership with domain teams.

Category: Overview

Why organize data by domain?

It reflects real business language and processes, improving clarity, accountability, and change resilience.

Category: Relevancy

How does Domain-Oriented Data relate to DDD?

It applies DDD principles—bounded contexts, ubiquitous language—to data modeling and ownership.

Category: Relation

How do domains interoperate?

Via contracts, shared semantics, and standards, often enforced by governance-as-code and APIs.

Category: HowTo

What is a common mistake when modeling Domain-Oriented Data?

Forcing a global canonical model that erases necessary domain differences.

Category: Mistakes

What risks exist with domain orientation?

Inconsistent semantics and duplicated metrics if cross-domain coordination is weak.

Category: Risk

How do you start adopting Domain-Oriented Data?

Identify bounded contexts, define glossaries and contracts, and pilot key data products.

Category: HowTo

What skills are required?

Data modeling, domain analysis, stewardship, and platform integration skills.

Category: Requirements

What competes with Domain-Oriented Data?

Enterprise canonical models and centralized ownership, which can hinder agility.

Category: Alternatives