🏷️Lakehouse Domain

NEW

Also known as: Domain-oriented Lakehouse, Data Mesh Domain

A business-aligned domain that owns and operates lakehouse data products with autonomous governance, standards, and pipelines within a platform like Microsoft Fabric.

DESCRIPTION

A Lakehouse Domain groups lakehouse resources by business capability, aligning with data mesh principles of domain ownership and self-serve data infrastructure. Each domain curates authoritative data products—tables, models, and pipelines—exposed through consistent interfaces. Domains enforce local governance while conforming to enterprise standards for interoperability, security, and discoverability. In Microsoft Fabric, domains map to workspaces and items, easing collaboration and lifecycle management. This structure reduces central bottlenecks and enables scalable analytics across federated teams.

ALTERNATIVE DEFINITIONS

Microsoft Learn

Domains in Microsoft Fabric are logical groupings that align items to business areas for ownership, governance, and discovery.

Defines domains as organizational constructs aligned to business areas.

Source

Thoughtworks (Zhamak Dehghani)

Data mesh advocates domain-oriented ownership, where data is treated as a product owned by cross-functional domain teams.

Emphasizes domain ownership and data-as-a-product philosophy.

Source

RELATED TERMS

Decentralized Data Architecture Data Lakehouse OneLake Data Product Domain-Driven Ownership Microsoft Fabric Governance Data Discovery Platform Self-Service Business Intelligence Data Architecture

COMPETING TERMS

Centralized Lakehouse Enterprise Data Warehouse

RELATIONS

• Broader: Domain

KNOWLEDGE AREAS

Data Architecture Data Management Data Engineering Data Products Cloud

TARGET AUDIENCE

Data Architect Data Engineer Analytics Engineer Data Governance Manager Chief Data Officer Data Strategy Consultant

EXTERNAL SOURCES

• Wikipedia - Data lakehouse
• Microsoft Learn - Fabric domains concept
• Thoughtworks - Data mesh principles
• Databricks - Lakehouse overview

TOP QUESTIONS

Why adopt a Lakehouse Domain structure?

It enables domain teams to own data products end-to-end, improving accountability, agility, and scalability while aligning to data mesh principles.

Category: Relevancy

How does a Lakehouse Domain relate to data mesh?

It operationalizes domain-oriented ownership and data-as-a-product within a lakehouse platform, enabling decentralized control with shared standards.

Category: Context

What governance is needed for a Lakehouse Domain?

Define ownership, quality SLAs, security policies, and interoperability standards. Use catalogs and lineage for discoverability and trust.

Category: Governance

What’s a common mistake when implementing a Lakehouse Domain?

Creating domains without clear business boundaries or product SLAs leads to confusion and inconsistent quality.

Category: Mistakes

How do domains publish data products?

They expose well-documented tables, models, and APIs through catalogs with contracts, versioning, and endorsements.

Category: Usage

What is the main risk of fragmented domains?

Duplication and inconsistent definitions can emerge. Mitigate with shared standards, federated governance, and semantic alignment.

Category: Risks

How does Fabric support Lakehouse Domains?

Fabric domains and workspaces map items to business areas, providing RBAC, item permissions, pipelines, and discoverability.

Category: Platform

How to measure success of a Lakehouse Domain?

Track product adoption, SLA adherence, incident rates, and consumer satisfaction. Monitor reuse and time-to-insight.

Category: Metrics

What competes with Lakehouse Domain organization?

Centralized lakehouses or monolithic EDWs concentrate ownership in platform teams, trading autonomy for uniformity.

Category: Alternatives