Overview
Direct Answer
Multi-tenancy is a cloud architecture pattern in which a single software instance and shared infrastructure serve multiple independent customers (tenants), with logical data isolation enforced at the application or database layer. Each tenant's data, configuration, and user experience remain isolated and inaccessible to others despite using the same underlying system.
How It Works
The architecture uses logical partitioning rather than dedicated physical separation. A single application codebase manages multiple tenant contexts, routing requests based on tenant identifiers embedded in authentication tokens, URLs, or headers. Database schemas may use row-level security, separate schemas within a shared database, or virtualised storage partitions to enforce data boundaries while maintaining resource efficiency.
Why It Matters
Multi-tenancy reduces infrastructure costs and operational overhead by consolidating compute, storage, and database resources across many customers. It enables faster deployment cycles and simplified maintenance since updates propagate to all tenants simultaneously, improving time-to-value and reducing compliance audit complexity across a normalised environment.
Common Applications
SaaS platforms such as CRM systems, project management tools, and business intelligence software typically employ this pattern. Email services, collaboration platforms, and human resources management systems leverage multi-tenancy to serve thousands of organisations cost-effectively from unified infrastructure.
Key Considerations
Practitioners must carefully implement tenant isolation to prevent data leakage through inadequate filtering, shared caches, or side-channel vulnerabilities. Performance noisy-neighbour effects—where one tenant's workload degrades others' experience—require robust resource quotas and quality-of-service controls.
More in Cloud Computing
Cloud Computing
Service ModelsThe delivery of computing services — servers, storage, databases, networking, software — over the internet on demand.
Serverless Computing
Service ModelsA cloud execution model where the provider dynamically allocates resources, charging only for actual compute time used.
Cloud Orchestration
Service ModelsThe automated arrangement, coordination, and management of complex cloud computing systems and services.
Disaster Recovery as a Service
Deployment & OperationsA cloud computing model that enables the replication and recovery of infrastructure and data in the cloud.
Infrastructure as a Service
Service ModelsCloud computing model providing virtualised computing resources like servers, storage, and networking over the internet.
Microservices
Architecture PatternsAn architectural style structuring an application as a collection of loosely coupled, independently deployable services.
FinOps
Strategy & EconomicsA cultural practice combining technology, finance, and business to manage cloud costs through data-driven decision making.
Container
InfrastructureA lightweight, portable software package that bundles application code with all its dependencies for consistent execution.