Asana: Architecture, Luna & Task Multi-Homing
A systems teardown of Asana: how Luna reactive data synchronization, real-time object graph caching, and task multi-homing across multiple projects pioneered modern work management.
Custom reactive framework keeping client object models identical to server state.
Single task entities can reside simultaneously in dozens of distinct projects.
Bi-directional push infrastructure streaming field updates instantly.
Asana Deep-Dive Chapters
The Graph Behind Multi-Project Task Living
The signature technical feature of Asana is multi-homing: a single task can belong to an engineering backlog, a marketing product launch timeline, and an executive OKR tracking board simultaneously. When a developer changes the due date or marks the task complete on their private list, the task updates synchronously across all parent projects.
Under the hood, Asana does not duplicate rows: it models work as a bipartite graph of tasks and containers. To make this feel instant in the browser, Asana developed Luna (and later migrated to React/TypeScript on top of its in-memory graph runtime), prefetching dependent task nodes and maintaining real-time WebSocket state channels.