NEW
Also known as: Business Domains
Business-aligned areas of responsibility that own and steward related datasets and data products.
DESCRIPTION
Data domains group datasets and responsibilities according to business capabilities and bounded contexts. They clarify ownership, stewardship, and accountability for data products and services. Domains enable autonomy while supporting cross-domain interoperability via contracts and standards. Clear boundaries reduce ambiguity and duplicate metrics. Domains should maintain glossaries and SLAs and coordinate with governance bodies. They are central to data mesh and domain-driven design. Effective domain design balances business reality with integration requirements. Domains evolve as organizations restructure or strategies change.
ALTERNATIVE DEFINITIONS
Wikipedia
In software engineering, a domain is a sphere of knowledge, influence or activity.
Provides a general definition of domain scope and context.
Martin Fowler
Bounded contexts define explicit boundaries within which a domain model applies, helping to partition a system.
Connects domains to bounded contexts for clarity.
Thoughtworks Technology Radar
Data mesh organizes data around domains to decentralize ownership and scale analytics.
Positions domains as the organizing unit in data mesh.
RELATED TERMS
Domain-Driven Design Domain-Oriented Data Decentralized Data Architecture Data Glossary Data Product Manager Domain-Driven Ownership
COMPETING TERMS
Functional Silos
KNOWLEDGE AREAS
Domain & Business Context Data Management Data Governance Data Architecture
TARGET AUDIENCE
Information Analyst Data Steward Data Architect Chief Data Officer Data Strategy Consultant Enterprise Architect
EXTERNAL SOURCES
- Wikipedia - Domain (software engineering)
- Martin Fowler - Bounded context explanation
- Martin Fowler - Data mesh and domains
- DAMA International - DMBOK data management body
TOP QUESTIONS
What are Data Domains?
They are business-aligned areas owning related datasets and data products, defined by capabilities or bounded contexts.
Category: Overview
Why use Data Domains?
They clarify ownership, speed delivery, and align semantics with business realities.
Category: Relevancy
How are domains defined?
By analyzing business capabilities, value streams, and shared vocabulary to establish clear boundaries.
Category: HowTo
What is a common mistake when defining domains?
Mapping domains to organizational charts rather than to stable business capabilities.
Category: Mistakes
How do domains coordinate?
Through governance councils, shared contracts, and standardized interfaces to ensure interoperability.
Category: Management
What risks exist with Data Domains?
Overlapping responsibilities and inconsistent metrics if boundaries and stewardship are unclear.
Category: Risk
How do domains relate to data mesh?
They are the organizing unit for ownership and product delivery in data mesh.
Category: Relation
What competes with domain organization?
Functional silos or centralized owners that disconnect data from business context.
Category: Alternatives
How do you measure domain effectiveness?
Track product SLAs, adoption, incident rates, and cross-domain integration success.
Category: Measurement