Multitenancy
Multitenancy is an architecture in which multiple independent tenants share an application or computing infrastructure while their data, resources, or operations remain logically isolated.
Fundamentals of Cybersecurity
Multi-tenancy is an architecture in which multiple tenants share infrastructure or a service while maintaining logical separation of their data and access.
- How it is used
- Describes how public-cloud customers can run workloads on shared physical servers while considering tenant isolation.
- How deep it goes
- Defines shared-resource tenancy and compares VM and container isolation, without detailing tenant-separation mechanisms.
- Examples
- Uses a physical server hosting several customers’ workloads and a VM-versus-container comparison to illustrate the trade-off.
- What you can do after
- Evaluate/understand it by distinguishing shared infrastructure from tenant isolation and checking provider–customer responsibilities.
Read how Fundamentals of Cybersecurity explains multitenancy →
Designing Deep Learning Systems: A guide for software engineers
An application that serves multiple tenants while keeping their data, configuration, or usage contexts logically separated.
- How it is used
- Separates user or group activities in HPO and serves tenant-specific models through a shared prediction application.
- How deep it goes
- Explains resource isolation and a model-cache architecture, stopping short of detailed tenancy boundaries or isolation mechanisms.
- Examples
- Uses a chatbot serving schools or retailers, tenant-trained intent models, and a cached multi-model prediction service.
- What you can do after
- Apply it by isolating tenant activities and routing prediction requests to the corresponding tenant-specific model.
Read how Designing Deep Learning Systems: A guide for software engineers explains multitenancy →
Google Anthos in Action
Multitenancy is an architecture in which multiple teams or tenants share a platform while retaining logical separation of their workloads and resources.
- How it is used
- Organizes shared Kubernetes clusters so operators can manage multiple tenants while preserving logical workload and resource separation.
- How deep it goes
- Explains namespace boundaries and namespaced controls, then identifies RBAC, quotas, network policies, and security resources without detailing their implementation.
- Examples
- Uses sales namespaces, namespace-qualified service DNS names, and centralized dashboards spanning multicloud or hybrid clusters.
- What you can do after
- Designs tenant boundaries with namespaces and selects access, quota, network, and security controls for safer shared clusters.
Platform Engineering on Kubernetes
Multi-tenancy is an architecture in which multiple tenants share underlying infrastructure while maintaining controlled separation of resources and access.
- How it is used
- Frames tenant boundaries and isolation as early platform-architecture decisions for teams sharing Kubernetes infrastructure.
- How deep it goes
- Compares namespaces, clusters, and vcluster through concrete benefits, limitations, API boundaries, RBAC, and resource quotas.
- Examples
- Uses namespace boundaries, separate clusters, and virtual clusters created through Helm or the vcluster CLI as implementation examples.
- What you can do after
- Evaluate tenancy requirements and choose namespaces, vcluster, or separate clusters for a Kubernetes platform.
Read how Platform Engineering on Kubernetes explains multitenancy →
Grokking Software Architecture
Multi-tenancy is an architecture in which a shared software system serves multiple customers or tenant organizations while maintaining separation of their data and workloads.
- How it is used
- Explains why architects must account for shared physical infrastructure when deploying applications in the public cloud.
- How deep it goes
- Defines shared infrastructure and illustrates noisy-neighbor effects, but stops short of detailing mitigation techniques.
- Examples
- Uses an apartment-sharing analogy and a startup consuming bandwidth or disk speed to illustrate resource contention.
- What you can do after
- Evaluate shared-cloud deployment risk by recognizing that another tenant’s resource use can slow an otherwise well-written application.
Read how Grokking Software Architecture explains multitenancy →
Also covered in
- Software Security for Developers
- Acing the CCNA Exam: Volume 2 Advanced Networking and Security
- Spring Security in Action, Second Edition
- Just Use Postgres!
- Authorization in Action
- Amazon Web Services in Action, Third Edition: An in-depth guide to AWS
- Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
- AI Agents and Applications
- Build Financial Software with Generative AI (From Scratch)
- React in Depth
- Digital Twins in Action
- The Cloud at Your Service: The when, how, and why of enterprise cloud computing
What to know first
- authorizationAuthorization is the determination of which actions or resources an identity or other entity is permitted to access under defined permissions or policies.
- authenticationAuthentication is the process of verifying the claimed identity of a user, service, device, or other entity.
- complianceCompliance is conformity with applicable legal, regulatory, contractual, policy, or other governing requirements.
- isolationIsolation is the separation of components, processes, resources, or contexts to limit interaction, interference, or the propagation of effects between them.
Related concepts
- cloud service modelkind of · A cloud service model classifies cloud offerings by the capabilities provided and the operational responsibilities retained by the provider and customer.
- cloud computingconfigured by · Cloud computing is a model for on-demand network access to shared computing resources and services that can be provisioned and scaled as needed.
- namespaceproduced by · A global namespace is a top-level naming context that binds identifiers defined at the outermost level and distinguishes them from names in nested scopes.
- openid connectuses · OpenID Connect is an identity layer built on OAuth 2.0 that enables clients to authenticate end users and obtain standardized identity claims.
- private cloudused by · A private cloud is a cloud computing environment dedicated to the use of a single organization and its authorized consumers.
Questions about multitenancy
What is multitenancy?
Multitenancy is an architecture in which multiple independent tenants share an application or computing infrastructure while their data, resources, or operations remain logically isolated.
Which Manning books explain multitenancy?
Fundamentals of Cybersecurity, Designing Deep Learning Systems: A guide for software engineers, Google Anthos in Action, Platform Engineering on Kubernetes and Grokking Software Architecture.
What should I know before learning multitenancy?
Manning books that teach multitenancy usually introduce authorization, authentication, compliance and isolation first.
What is multitenancy a kind of?
Multitenancy is a kind of cloud service model. A cloud service model classifies cloud offerings by the capabilities provided and the operational responsibilities retained by the provider and customer.
What is multitenancy also called?
Multitenancy is also called multi-tenancy.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.




