How do you design a scalable, multi-tenant extension application on BTP?

A multi-tenant extension serves multiple customers/business units from one shared application deployment, requiring careful architectural separation between what's shared (application code, infrastructure) and what must remain isolated (each tenant's data and configuration).

flowchart TB
    A[Shared Application Code] --> B[Tenant A - isolated data/config]
    A --> C[Tenant B - isolated data/config]
    A --> D[Tenant C - isolated data/config]

Key design decisions include: how tenant data isolation is enforced (separate schemas, row-level security, or fully separate database instances per tenant), how the application scales horizontally as tenant count grows, and how tenant-specific configuration/customization is supported without forking the shared codebase per tenant. BTP's multitenancy services provide some of this scaffolding out of the box, but the architect still needs to design the specific isolation and scaling model appropriate to the extension's data sensitivity and expected scale.