liveBook · Manning

Multitenancy

Also called multi-tenancy

Multitenancy is an architecture in which multiple independent tenants share an application or computing infrastructure while their data, resources, or operations remain logically isolated.

How 5 Manning books explain it

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.

Read how Google Anthos in Action explains multitenancy →

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

What to know first

Related concepts

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.