Decision tree

Shared, cell-based, or single-tenant.

Tenancy determines blast-radius, cost shape, deploy cadence, and audit. Pick the wrong one and you'll re-platform mid-growth. This tree walks uniform-vs-heterogeneous load, isolation needs, and the head-tenant count that flips the model.

4 questions max6 end-states~3-4 minShareable via URL hash

If JavaScript is disabled — the questions in this tree

  1. Will any one customer's load, blast-radius, or compliance need to exceed the others by >10x?
  2. Are you under hard data-isolation constraints (per-tenant encryption keys, sovereign data residency, regulator-required dedicated storage)?
  3. Is that big customer's stack legitimately different (different version, custom integrations, contractual SLO that the shared stack can't meet)?
  4. How many tenants are on the heterogeneous “head”?

Re-enable JavaScript to step through interactively. Or jump straight to the related artefacts: diagnostics · reference architectures · writing.

Also on this site