Canva Architecture Decision

Overview

Select the smallest topology that preserves backend OAuth, per-user token isolation, asynchronous job reconciliation, and policy-controlled data handling. Treat scale thresholds as measured local evidence, not Canva product limits.

Prerequisites

• Expected operations, traffic shape, tenants, and recovery objectives
• Data classification, retention policy, and secret backend
• Current scopes, capabilities, preview dependencies, and deployment constraints

Instructions

Step 1: Map trust boundaries

Identify browser, backend, token store, job ledger, worker, data store, and Canva API boundaries. Mark every place customer content or credentials could cross.

Step 2: Choose the base shape