100% Free Forever
AI-Powered Learning
Industry Expert Content
Certificates & Badges
Learn At Your Own Pace

Multi-Tenant Database Design Cheat Sheet

Multi-Tenant Database Design Cheat Sheet

Multi-tenant database architecture patterns covering shared-schema with tenant_id, schema-per-tenant, database-per-tenant, and RLS.

2 PagesAdvancedMay 12, 2026

Shared Schema with Row-Level Security

The most common pattern: one schema, a tenant_id column, enforced by Postgres RLS.

sql
CREATE TABLE invoices (    id UUID PRIMARY KEY DEFAULT gen_random_uuid(),    tenant_id UUID NOT NULL,    amount NUMERIC NOT NULL,    created_at TIMESTAMPTZ DEFAULT now());CREATE INDEX ON invoices (tenant_id);ALTER TABLE invoices ENABLE ROW LEVEL SECURITY;CREATE POLICY tenant_isolation ON invoices    USING (tenant_id = current_setting('app.current_tenant')::UUID);-- Set per-connection/session before running app queriesSET app.current_tenant = '3f2504e0-4f89-11d3-9a0c-0305e82c3301';

Schema-per-Tenant Provisioning

Stronger isolation via a dedicated schema, with shared connection pooling.

sql
-- Provisioning a new tenantCREATE SCHEMA tenant_acme;SET search_path TO tenant_acme;CREATE TABLE invoices (LIKE public.invoices_template INCLUDING ALL);-- Application connects and sets search_path per request-- e.g. in Node: await client.query('SET search_path TO tenant_acme');-- Migrations must be looped across all tenant schemas-- for schema in $(psql -tAc "SELECT nspname FROM pg_namespace WHERE nspname LIKE 'tenant_%'"); do#   psql -c "SET search_path TO $schema; \i migration.sql"# done

Application-Layer Tenant Scoping (Prisma middleware example)

Defense-in-depth: enforce tenant scoping in the ORM even when RLS is also in place.

typescript
prisma.$use(async (params, next) => {  const tenantId = getCurrentTenantId(); // from request context / AsyncLocalStorage  if (params.model === 'Invoice') {    if (params.action === 'findMany' || params.action === 'findFirst') {      params.args.where = { ...params.args.where, tenantId };    }    if (params.action === 'create') {      params.args.data.tenantId = tenantId;    }  }  return next(params);});

Isolation Models — Tradeoffs

The three standard multi-tenant data isolation strategies.

  • Shared schema + tenant_id- cheapest to operate, easiest to scale, weakest isolation; needs RLS or app-layer enforcement
  • Schema-per-tenant- stronger isolation, easier per-tenant backup/restore, but migrations and connection pooling get harder past hundreds of tenants
  • Database-per-tenant- strongest isolation and blast-radius containment, best for compliance-heavy tenants, but highest operational overhead
  • Row-Level Security (RLS)- Postgres feature that transparently filters rows by policy; defense-in-depth against a missed WHERE clause
  • Noisy neighbor- one tenant's load degrading others' performance; mitigated by resource quotas or moving big tenants to dedicated DBs
  • Tenant sharding- hybrid: group tenants across multiple shared-schema databases based on size/tier

RLS Driven by JWT Claims (Supabase/Postgres pattern)

Bind the RLS policy to claims extracted from a signed JWT instead of a manually SET session variable, so isolation holds even if app code forgets to set it.

sql
CREATE OR REPLACE FUNCTION auth.tenant_id() RETURNS UUID AS $$  SELECT NULLIF(current_setting('request.jwt.claims', true)::json->>'tenant_id', '')::UUID;$$ LANGUAGE sql STABLE;CREATE POLICY tenant_isolation_select ON invoices  FOR SELECT USING (tenant_id = auth.tenant_id());CREATE POLICY tenant_isolation_insert ON invoices  FOR INSERT WITH CHECK (tenant_id = auth.tenant_id());-- Force RLS even for the table owner role (critical: owners bypass RLS by default)ALTER TABLE invoices FORCE ROW LEVEL SECURITY;

Tenant Context in a Pooled Connection (PgBouncer transaction mode)

SET LOCAL scopes the tenant GUC to the current transaction only, which is mandatory under transaction-mode pooling where connections are shared across tenants between transactions.

typescript
async function withTenant<T>(tenantId: string, fn: (tx: PoolClient) => Promise<T>): Promise<T> {  const client = await pool.connect();  try {    await client.query('BEGIN');    // SET LOCAL, not SET — it auto-resets at COMMIT/ROLLBACK, safe to reuse the connection    await client.query('SET LOCAL app.current_tenant = $1', [tenantId]);    const result = await fn(client);    await client.query('COMMIT');    return result;  } catch (err) {    await client.query('ROLLBACK');    throw err;  } finally {    client.release();  }}

Composite Foreign Keys to Prevent Cross-Tenant Joins

Make tenant_id part of every primary key and foreign key so the database itself rejects a row referencing another tenant's parent — RLS alone doesn't stop this at the FK-constraint level.

sql
CREATE TABLE accounts (    id UUID DEFAULT gen_random_uuid(),    tenant_id UUID NOT NULL,    name TEXT NOT NULL,    PRIMARY KEY (tenant_id, id));CREATE TABLE invoices (    id UUID DEFAULT gen_random_uuid(),    tenant_id UUID NOT NULL,    account_id UUID NOT NULL,    amount NUMERIC NOT NULL,    PRIMARY KEY (tenant_id, id),    -- Composite FK forces account_id to belong to the SAME tenant_id    FOREIGN KEY (tenant_id, account_id) REFERENCES accounts (tenant_id, id));

Fan-Out Migrations Across Database-per-Tenant

Concurrent, capped-parallelism migration runner for the database-per-tenant model, with per-tenant failure isolation.

python
import asyncioimport asyncpgasync def migrate_tenant(dsn: str, sql: str, sem: asyncio.Semaphore) -> tuple[str, Exception | None]:    async with sem:        conn = await asyncpg.connect(dsn)        try:            async with conn.transaction():                await conn.execute(sql)            return dsn, None        except Exception as e:            return dsn, e        finally:            await conn.close()async def migrate_all(tenant_dsns: list[str], sql: str, max_concurrency: int = 10):    sem = asyncio.Semaphore(max_concurrency)    results = await asyncio.gather(*(migrate_tenant(d, sql, sem) for d in tenant_dsns))    failed = [(dsn, err) for dsn, err in results if err]    if failed:        raise RuntimeError(f"{len(failed)} tenant migrations failed: {failed}")

Advanced Isolation Pitfalls

Failure modes that show up only after the basic RLS/schema setup is already in production.

  • RLS + BYPASSRLS rolesbackground jobs and superuser connections silently bypass every policy unless FORCE ROW LEVEL SECURITY is set on the table
  • Leaky query plansPostgres can push a non-tenant-scoped filter below the RLS check in rare planner cases; always verify with EXPLAIN that tenant_id is applied first
  • Sequence/identity collisionsshared auto-increment sequences across schema-per-tenant clones can leak tenant cardinality; prefer UUIDs or per-tenant sequences
  • Cross-tenant analyticsreporting queries that need to aggregate across all tenants require a separate role with RLS bypass, audited and never exposed to app traffic
  • Backup/restore blast radiusin shared-schema mode, a point-in-time restore for one tenant's bad migration restores every tenant; database-per-tenant avoids this at the cost of ops overhead
  • Tenant deprovisioningDELETE ... WHERE tenant_id = ? on large shared tables causes long-running locks; use batched deletes or partition-by-tenant with DROP PARTITION
  • Connection pooling limitsdatabase-per-tenant multiplies connection pool count; a pooler-per-tenant-group (e.g. PgBouncer per shard) is needed past a few hundred tenants
Pro Tip

Enforce tenant isolation at two layers, not one — RLS policies in Postgres plus tenant scoping in your ORM/query layer — because a single forgotten `WHERE tenant_id = ?` in application code is the single most common cause of real-world cross-tenant data leaks.

Was this cheat sheet helpful?

Explore Topics

#MultiTenantDatabaseDesign#MultiTenantDatabaseDesignCheatSheet#Database#Advanced#Shared#Schema#Row#Level#Databases#CheatSheet#SkillVeris

Frequently Asked Questions

21 categories · pick one to explore

Does SkillVeris have a tech blog, and what does it cover?
Yes, the SkillVeris blog has over 500 articles covering AI and machine learning, programming, web development, DevOps, cloud, security, databases and career guidance. Articles are practical and answer-first, and many use the Learn Through Hobbies approach, teaching technical concepts through cricket, music, gaming or cooking analogies. Everything is free to read.
What is the SkillVeris tech glossary and how big is it?
The SkillVeris glossary is a free reference of roughly 2,000-plus technology terms, each with a clear plain-language definition. It spans AI, programming, web, DevOps, cloud, security and database vocabulary, so whenever a lesson, article or job description uses jargon you do not recognise, the glossary gives you a fast, reliable answer.
Are the developer cheat sheets on SkillVeris free to download?
The cheat sheets are completely free to use, like everything else on SkillVeris. Each sheet condenses a language or tool into its essential syntax, commands and patterns for quick reference while coding. They are designed for rapid lookup during real work, complementing the deeper explanations found in study notes and courses.
Which programming references and cheat sheets are available?
Cheat sheets cover the platform's main domains, including programming languages, AI and ML tooling, web development, DevOps, cloud, security and databases, matching the topics of the 37 live courses. Each sheet lists related reading links and hashtags, so you can jump from a quick reference into fuller study notes or blog articles.
How do I find the meaning of a technical term quickly?
Search the SkillVeris glossary, which holds around 2,000-plus terms with concise, plain-language definitions. Each entry gets to the point in its first sentence, then links to related reading like blog posts or study notes for deeper context. It is faster and more consistent than sifting through scattered search results.
Is the SkillVeris blog good for beginners learning to code?
Yes, many blog articles are written specifically for beginners, and the Learn Through Hobbies style makes them unusually approachable: you might learn Python concepts through cricket or understand APIs through cooking. With 500-plus articles across skill levels, beginners can start with fundamentals and keep reading as they advance, entirely free.
Can cheat sheets replace full courses for learning a language?
No, cheat sheets are references, not teaching tools; they assume you already understand the concepts and just need syntax or commands fast. To actually learn a language, take a structured SkillVeris course with its 24–40 lessons and assessments, then keep the cheat sheet beside you while practising in Code Lab.
How often are new blog articles published on SkillVeris?
The blog grows regularly and already exceeds 500 articles, with new posts added as courses launch and technologies evolve. Topics track the platform's catalogue across AI, programming, web development, DevOps, cloud and security, so checking the Blog section periodically surfaces fresh tutorials, explainers and career-focused pieces, all free to read.
Does the glossary cover AI and machine learning terms?
Yes, AI and machine learning vocabulary is a major part of the roughly 2,000-plus term glossary, covering everything from foundational terms to modern concepts around LLMs, RAG and MLOps. Definitions are plain-language and answer-first, which helps when dense AI papers or course lessons throw unfamiliar jargon at you.
Are there cheat sheets for interview preparation?
Cheat sheets work well as interview-day refreshers because they compress syntax, commands and key concepts into scannable references. For dedicated preparation, combine them with the SkillVeris interview questions feature, which includes readiness scoring, plus study notes for depth. Reviewing a relevant cheat sheet just before an interview steadies recall under pressure.
Can I read the tech blog without signing up?
Yes, the blog is freely readable, and SkillVeris never charges for content. All 500-plus articles are open, covering tutorials, concept explainers and career advice. Creating a free account adds value elsewhere on the platform, like course progress tracking and certificates, but reading the blog requires no commitment at all.
How is the SkillVeris glossary different from Wikipedia?
The glossary is purpose-built for learners: definitions are short, plain-language and answer-first, sized for a quick lookup mid-lesson rather than a deep encyclopedic read. Entries also cross-link to related SkillVeris study notes, blog posts and courses, so a definition becomes a doorway into structured learning instead of a dead end.
Do blog articles use the Learn Through Hobbies method?
Many blog articles teach technical topics through hobby analogies, a hallmark of the SkillVeris blog, so you will find articles explaining programming through cricket, machine learning through music, or system design through cooking. The analogy is the teaching device; the article still delivers the real technical concept underneath.
Where can I find quick programming references while coding?
Open the SkillVeris cheat sheets, which are built exactly for that moment: compact, scannable references for syntax, commands and common patterns across languages and tools. Keep the relevant sheet in a browser tab while you work in Code Lab or your own editor, and dip into the glossary for terminology.
Is there a glossary entry for terms I meet in job descriptions?
Very likely yes, with roughly 2,000-plus terms across AI, programming, web, DevOps, cloud, security and databases, the glossary covers most jargon that appears in tech job descriptions. Decoding a listing this way helps you judge role fit honestly and prepares you to discuss those terms in interviews.
Are the blog articles written for the Indian tech audience?
The blog serves Indian learners plus a worldwide audience. Content stays globally relevant while acknowledging realities that matter in India, such as free access being essential for students and freshers, and career guidance that connects naturally to the SkillVeris jobs portal, which aggregates roles across India, UK, USA, Germany and Remote.
Can I suggest a topic for the blog or glossary?
SkillVeris content grows in response to what learners need, so feedback is welcome through the platform's support channels. If a term is missing from the glossary or a topic deserves an article, telling the team helps prioritise it. Meanwhile, the AI Mentor can answer the question immediately, 24/7, at any depth.
Do cheat sheets and glossary entries link to deeper learning?
Yes, every cheat sheet and glossary entry carries related reading links into study notes, blog articles and courses, plus concept hashtags for discovering similar content. This cross-linking means a thirty-second lookup can smoothly become a structured learning session whenever you decide you want more than a quick answer.
What makes SkillVeris programming references trustworthy?
The references are written to strict internal quality standards, kept consistent with the platform's 37 live courses, and never padded with invented statistics or hype. Definitions and cheat sheets are reviewed against the same content contracts that govern courses, and the answer-first style makes any inaccuracy easy to spot and correct.
How do the blog, glossary and cheat sheets fit into my learning routine?
Use them as satellites around your main course: read blog articles for context and motivation, hit the glossary the instant jargon appears, and keep cheat sheets open while coding. Together with study notes, Code Lab and the 24/7 AI Mentor, they turn passive reading into a complete, free learning system.

What Learners Say

Real journeys from the SkillVeris community — swipe for more.

SkillVeris taught me Python through Cricket. Now I’m building real projects and feeling confident!
Arjun S. · B.Tech Student
The best platform for hobby-based learning. Concepts finally stick.
Priya R. · Data Analyst
I went from zero coding to a portfolio of projects — all by learning through my love for gaming. Landed my first internship!
Kabir M. · CS Undergraduate
Trending Topics50 popular tags — tap to explore
Trending CoursesAll 37 free courses — tap to browse