Real-Time Analytics Platform · View 06 of 21 · Structure

Tenancy and Workload Isolation

Where the tenant boundary sits at each layer, and how one tenant's traffic or one team's ad-hoc query is prevented from degrading everybody else.

Editable source SVG draw.io All views

Isolation model

Shared tier: one namespace and one ADX database, separated by partition key and row-level security
Premium tier: dedicated Event Hubs namespace, dedicated ADX database, its own follower
Ad-hoc and export workloads are physically separated onto a second follower cluster

Why not a cluster per tenant

Per-tenant clusters would multiply cost by tenant count for no isolation gain below the premium tier
Row-level security plus workload groups covers the stated requirement at a fraction of the spend
Promotion from shared to premium is a migration path, not a re-architecture

Residual risk

A shared-tier tenant with a hot partition key can saturate ingestion for its neighbours
Mitigation is APIM quota plus a documented promotion trigger, not prevention
Row-level security is enforced in one place; a policy defect is a cross-tenant exposure

◀ Integration and Interface Catalogue All views Event Data Flow ▶