# Scaling beyond one: How Airbnb evolved its data architecture for a multi-product world

[Airbnb](https://yomu.fyi/company/airbnb) · Patrick Lam · Jun 9, 2026

## Summary

To support its expansion from Homes into Experiences and Services, Airbnb evolved its offline data warehouse architecture to balance domain-specific needs with organizational consistency. Rather than enforcing a single global pattern, data teams adopted a framework of foundational principles that paired separate data models for unique product features with monolithic models for cross-cutting domains like payments and messaging.

## Takeaways

- Airbnb enforced three foundational rules: no hybrid models within a domain, strict identifier naming conventions based on the chosen pattern, and clear namespace separation.
- Domains with unique attributes and workflows (such as listings and availability) used separate models, whereas shared concepts (such as payments, messaging, and support) used monolithic models.
- The offline warehouse functions as an essential translation layer between online transactional databases and downstream analytics, requiring careful deprecation strategies like dual pipeline validation to manage data debt.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [Data Pipelines](https://yomu.fyi/topic/data-pipelines), [Migrations](https://yomu.fyi/topic/migration), [Scalability](https://yomu.fyi/topic/scalability)

[Read original post](https://medium.com/airbnb-engineering/scaling-beyond-one-how-airbnb-evolved-its-data-architecture-for-a-multi-product-world-6125645d470c)