Multiplayer Collaborative Canvas · View 07 of 23 · Structure
The rule between layers
- Everything above the Session layer is a replica; everything below it except the Record layer is derived. That single sentence decides what is backed up, what is rebuilt, and what is simply lost on restart (view 11).
- The Real-time layer is split from the Session layer on purpose: presence coalescing and viewer broadcast scale with connections, while sequencing scales with documents.
- The Platform layer is on the admission path, not the edit path. A control-plane outage must not stop a document that is already open (ADR-14).
Omitted deliberately
- Every layer writes Azure Monitor and reads Entra ID; drawing those edges would say nothing the reader does not assume.
- The export and search consumers hang off the Derived layer and appear in views 09 and 10.
Risks
- A layered drawing invites the belief that a request passes through every layer. It does not: a viewer never enters the Session layer, and presence never reaches the Record layer (view 16).