Tenant
A tenant is an independently managed organization, customer, user group, or workload whose data, access, configuration, and resources are logically isolated within a shared system.
Software Security for Developers
A tenant is an independently scoped organization or customer population sharing an identity system while retaining separate users, configuration, and access boundaries.
- How it is used
- Supports SaaS, enterprise, customer, vendor, and partner platforms that share identity infrastructure while isolating organizations.
- How deep it goes
- Explains tenant separation, routing, claims, login methods, roles, and sessions, but stops short of implementation code.
- Examples
- Uses SaaS platforms, enterprise units, customer portals, multiple login providers, and tenant_id-bearing tokens.
- What you can do after
- Design tenant-aware identity flows with tenant-specific URLs, claims, login providers, roles, sessions, and permissions.
Designing Deep Learning Systems: A guide for software engineers
A customer organization that uses a shared application while maintaining a separate account and segregated data.
- How it is used
- Supports shared chatbot applications that isolate customer accounts and data while routing requests to tenant-specific models.
- How deep it goes
- Defines tenant identity and explains model routing, caching, and file serving without detailing implementation interfaces.
- Examples
- Uses schools and retail stores sharing a chatbot, separate datasets, tenant-specific models, and a cached prediction service.
- What you can do after
- Operate/configure a shared prediction service that selects tenant-specific models and caches their graphs and dependent data.
Read how Designing Deep Learning Systems: A guide for software engineers explains tenant →
Platform Engineering on Kubernetes
A tenant is a team, customer, or other independent consumer that shares a platform while requiring separated access and resources.
- How it is used
- Frames platform boundaries for teams and customers sharing Kubernetes resources.
- How deep it goes
- Compares namespace and cluster isolation, but stops short of selecting one universal tenancy model.
- Examples
- Uses namespaces, RBAC roles, resource quotas, shared API servers, and separate clusters as concrete tenancy mechanisms.
- What you can do after
- Evaluate isolation choices and define tenant guarantees for a Kubernetes platform.
Read how Platform Engineering on Kubernetes explains tenant →
Just Use Postgres!
A tenant is an independent customer or merchant whose data and operations are isolated within a shared multitenant system.
- How it is used
- Supports scalable SaaS applications by sharing infrastructure while isolating each customer’s data and operations.
- How deep it goes
- Defines tenants, compares table, schema, and database isolation, and demonstrates database creation without covering full administration.
- Examples
- Uses brewery and coffee-chain merchants, separate Postgres databases, database inventory output, and a connection command.
- What you can do after
- Operate database-level multitenancy by creating merchant databases, listing them, and connecting to a tenant database.
Related concepts
- multitenancyuses · Multitenancy is an architecture in which multiple independent tenants share an application or underlying infrastructure while their data, resources, or access remain logically separated.
- policy bundlehas part · A policy bundle is a validated, packaged collection of authorization policies prepared for versioned deployment and runtime evaluation.
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.