Partitioning for Multi-Tenancy — Isolation, Performance, and Maintenance

SaaS applications storing data for multiple tenants (companies, organisations) face a fundamental schema design question: one database per tenant, one schema per tenant, or one shared table with a tenant_id column? Partitioning by tenant offers a middle path that combines the operational simplicity of a shared table with the performance isolation of separate storage.