How deeply does Just Use Postgres! cover schema-level multitenancy?

Defines dedicated tenant schemas and contrasts isolation levels, but stops short of schema creation or permission configuration.

Schema-level multitenancy

As explained in Just Use Postgres!

Schema-level multitenancy gives each tenant a dedicated schema containing its own tables within one logical database.

Schema-level multitenancy gives each tenant a dedicated schema containing its own tables, while all tenant schemas remain within one logical PostgreSQL database. This isolates merchant data without creating a separate database for every tenant. section 2.1.1

Multitenancy can isolate tenant data at several database boundaries:

Table-level multitenancy stores all tenants in shared tables and distinguishes rows with a tenant identifier. section 2.1.1
Schema-level multitenancy gives every tenant separate tables inside its own schema. section 2.1.1
Database-level multitenancy gives every tenant a separate database, allowing tenant databases to be distributed across PostgreSQL servers. section 2.1.1

Merchant isolation

A brewery and a coffee chain can use the same platform without sharing business data. The demonstrated implementation chooses database-level isolation instead: separate databases named coffee_chain and brewery are created and inspected with psql. section 2.1.1

How Just Use Postgres! covers it

liveBook manning.com

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

Related concepts

multitenancykind of · Multitenancy is an architecture in which multiple independent tenants share an application or underlying infrastructure while their data, resources, or access remain logically separated.
database-level multitenancyalternative to · Database-level multitenancy gives each tenant a separate database within a database infrastructure.
table-level multitenancyalternative to · Table-level multitenancy is a database design in which multiple tenants’ records share tables and are distinguished by tenant-specific columns and query constraints.

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.