Multitenancy
Multitenancy is an architecture in which multiple independent tenants share an application or underlying infrastructure while their data, resources, or access remain logically separated.
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 →
Related concepts
- database tableuses · A database table is a relational database structure that organizes records into rows and defined columns.
- 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.
- namespaceproduced by · A namespace is a naming context or identifier space in which names are defined and resolved, distinguishing them from names in other contexts.
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.