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
Software as a Service
Service ModelsCloud computing model that delivers software applications over the internet on a subscription basis.
Function as a Service
Service ModelsA serverless cloud computing model where individual functions are executed in response to events.
Platform Engineering
Deployment & OperationsThe practice of building and maintaining internal developer platforms that provide self-service capabilities, standardised tooling, and golden paths for software delivery teams.
Private Cloud
Service ModelsCloud computing resources used exclusively by a single organisation, either on-premises or hosted by a third party.
Event-Driven Architecture
Architecture PatternsAn architecture pattern where the flow of the system is determined by events — significant changes in state.
Container Orchestration
InfrastructureThe automated management of containerised application deployment, scaling, networking, and availability across clusters of machines, with Kubernetes as the dominant platform.
API
Architecture PatternsApplication Programming Interface — a set of protocols and tools for building and integrating software applications.
Infrastructure as Code
Deployment & OperationsManaging and provisioning computing infrastructure through machine-readable configuration files rather than manual processes.