PATTERN Cited by 1 source

No hybrid data models

Intent

Prevent confusing, inconsistent situations where some products within a domain use combined data tables while others use separate tables, by requiring each domain to commit fully to one approach.

How it works

A domain's data model must be either completely separate by product type or completely monolithic. Mixing approaches within a single domain is prohibited. This binary choice is enforced as a foundational principle across the organization (Source: sources/2026-06-09-airbnb-scaling-beyond-one-data-architecture).

Rationale

• Half-separate/half-monolithic creates confusion about where to find data
• Makes the model harder to evolve when new products are added
• Consumers can't form reliable mental models of a domain's schema

Trade-offs

• Pro: Clear mental model for consumers — a domain is either unified or split
• Pro: Future scalability — the choice is coherent when adding product lines
• Con: Some domains have subdomains where the "other" choice would fit better
• Con: Forces binary decisions on nuanced situations

Seen in

• sources/2026-06-09-airbnb-scaling-beyond-one-data-architecture — Principle 1 of Airbnb's three-product data architecture framework