SAP BTP Multi-Tenancy — SaaS Architecture for Java Developers

Lesson 1.4 — BTP Multi-Tenancy Table of Contents 1. BTP Multi-Tenancy Model 2. Tenant Isolation Patterns 3. XSUAA in Multi-Tenant Context 4. CAP Multi-Tenancy Support (@sap/cds-mtxs) 5. Operational Concerns Top 5 Pitfalls What to Learn Next Summary: Multi-tenancy on SAP BTP enables building SaaS applications where a single deployment serves multiple customers (tenants) with data isolation, independent configuration, and per-tenant extensibility. This lesson covers the BTP multi-tenancy lifecycle, tenant isolation patterns, XSUAA identity zones, CAP's MTX framework, and operational concerns — compared with Spring Boot / Hibernate multi-tenancy patterns. 1. BTP Multi-Tenancy Model Core Concept In BTP's multi-tenancy model, your application is deployed once in a provider subaccount, and customer organizations subscribe from their own subaccounts: ┌─────────────────────────────────┐ │ Provider Subaccount │ │ (your SaaS app deployed) │ │ │ │ ┌────────────────────────────┐ │ │ │ App Instance