How deeply does Just Use Postgres! cover tenant?

Defines tenants, compares table, schema, and database isolation, and demonstrates database creation without covering full administration.

Tenant

As explained in Just Use Postgres!

A tenant is an independent customer or merchant whose data and operations are isolated within a shared multitenant system.

A tenant is an independent customer or merchant whose data and operations remain isolated inside a shared multitenant SaaS application. A brewery and a coffee chain can use the same eCommerce platform without sharing business data. section 2.1.1

Postgres multitenancy commonly separates tenant data at three levels:

Table level: store all tenants in shared tables and distinguish records with a tenant_id column. section 2.1.1
Schema level: give each tenant dedicated tables within its own schema in one logical database. section 2.1.1
Database level: give each tenant a dedicated database object, protected through roles and permissions. section 2.1.1

Separate merchant databases

Create one database for each merchant, then verify the instance contents: CREATE DATABASE coffee_chain; CREATE DATABASE brewery; SELECT datname FROM pg_database; The result lists both tenant databases alongside PostgreSQL’s default databases. Connecting with \c coffee_chain switches the session to the coffee-chain tenant.

How Just Use Postgres! covers it

liveBook manning.com

Read Just Use Postgres! on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Software Security for DevelopersA tenant is an independently scoped organization or customer population sharing an identity system while retaining separate users, configuration, and access boundaries.
liveBook manning.com

Designing Deep Learning Systems: A guide for software engineersA customer organization that uses a shared application while maintaining a separate account and segregated data.
liveBook manning.com

Platform Engineering on KubernetesA tenant is a team, customer, or other independent consumer that shares a platform while requiring separated access and resources.

Compare how 4 books explain tenant →

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.

This explainer was generated by Manning's knowledge graph from the text of Just Use Postgres!. The section links point to the parts of the book it draws on.