PricingLoginStart free
NestJS Enterprise Backend APIs · Lezione

Risoluzione del tenant tramite middleware e AsyncLocalStorage

Estragga e propaghi il tenant attivo nelle richieste usando il contesto di AsyncLocalStorage.

Lezione 1 di 413 passaggi

Risoluzione del tenant tramite middleware e AsyncLocalStorage è una lezione NestJS Enterprise Backend APIs gratuita su CoddyKit. Questa è la lezione 1 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento NestJS Enterprise Backend APIs, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso NestJS Enterprise Backend APIs include 4 lezioni in totale.

Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.

The Multi-Tenancy Problem

In a multi-tenant backend, one running instance serves many customers (tenants). Every request belongs to exactly one tenant, and almost every layer needs to know which one: the database connection, query filters, caches, audit logs, even outbound emails.

  • Passing a tenantId argument down through every service method is noisy and error-prone.
  • Forget it once in a query and you leak tenant A's data to tenant B — a critical security bug.

We need to resolve the tenant once at the edge of the request and propagate it implicitly to everything that runs during that request.

Where Does the Tenant Come From?

Resolution strategy depends on your routing model. Common sources, in order of how early they are available:

  • Subdomain: acme.api.example.com → tenant acme.
  • Header: X-Tenant-Id: acme (common for internal/service-to-service calls).
  • JWT claim: a tid claim inside the access token.
  • Path prefix: /t/acme/orders.

Whatever the source, the goal is to turn raw request data into a validated tenant identifier as early as possible — ideally in middleware, which runs before guards, interceptors, and controllers.

function resolveTenantFromHost(host: string): string | null {
  // acme.api.example.com -> "acme"
  const parts = host.split('.');
  if (parts.length < 3) return null;
  const sub = parts[0];
  return /^[a-z0-9-]+$/.test(sub) ? sub : null;
}

console.log(resolveTenantFromHost('acme.api.example.com')); // acme
console.log(resolveTenantFromHost('localhost'));            // null
console.log(resolveTenantFromHost('BAD!.api.example.com')); // null

Why Not Just Use the Request Object?

A naive approach is to attach the tenant to req and read req.tenantId everywhere. This works in controllers and guards but breaks down quickly:

  • Deep services would need the Request injected (@Inject(REQUEST)), forcing them to be request-scoped, which is contagious and hurts performance.
  • Code with no access to req — a repository helper, a logger formatter, a TypeORM subscriber — has no clean way to read it.

We want a way to ask "what tenant am I serving right now?" from anywhere in the async call stack, without threading req through. That is exactly what AsyncLocalStorage provides.

AsyncLocalStorage in 60 Seconds

AsyncLocalStorage (from Node's built-in async_hooks) gives you a per-request store that survives across await boundaries, timers, and callbacks. You call als.run(store, callback) once, and any code executed inside that callback — however deep, however async — can call als.getStore() to read the same store.

It is conceptually thread-local storage for Node's single-threaded async model. Each request gets its own isolated store; concurrent requests never see each other's data.

import { AsyncLocalStorage } from 'node:async_hooks';

const als = new AsyncLocalStorage<{ tenantId: string }>();

async function deepWork(): Promise<void> {
  await new Promise((r) => setTimeout(r, 10));
  const store = als.getStore();
  console.log('deep sees:', store?.tenantId);
}

async function handle(tenantId: string): Promise<void> {
  await als.run({ tenantId }, async () => {
    await deepWork();
  });
}

// Two concurrent "requests" stay isolated
Promise.all([handle('acme'), handle('globex')]);

Designing the Tenant Context Store

Wrap AsyncLocalStorage in a small, typed service so the rest of the app never touches Node internals directly. Keep the store shape minimal but extensible — at least the tenant id, plus anything else you want request-scoped (request id, user id).

  • run(store, cb) — enter a new context for one request.
  • get() — read the current tenant, throwing if called outside any context (fail loud, not silently global).

Making get() throw on a missing context is deliberate: a silent undefined tenant is how cross-tenant leaks happen.

import { AsyncLocalStorage } from 'node:async_hooks';
import { Injectable } from '@nestjs/common';

export interface TenantStore {
  tenantId: string;
  requestId: string;
}

@Injectable()
export class TenantContext {
  private readonly als = new AsyncLocalStorage<TenantStore>();

  run<T>(store: TenantStore, cb: () => T): T {
    return this.als.run(store, cb);
  }

  get(): TenantStore {
    const store = this.als.getStore();
    if (!store) {
      throw new Error('TenantContext accessed outside of a request scope');
    }
    return store;
  }

  get tenantId(): string {
    return this.get().tenantId;
  }
}

The Tenant Resolution Middleware

Middleware is the right place to resolve and open the context because it runs at the very start of the request, before guards and route handlers. The middleware:

  • Extracts the raw tenant hint (header, subdomain, etc.).
  • Validates it and rejects unknown tenants with 400/404.
  • Calls tenantContext.run(...) and invokes next() inside the callback so the entire downstream pipeline executes within the context.

The critical detail: next() must be called inside run(). If you call next() after run() returns, the context is already closed and every getStore() downstream returns undefined.

import { Injectable, NestMiddleware, BadRequestException } from '@nestjs/common';
import { Request, Response, NextFunction } from 'express';
import { randomUUID } from 'node:crypto';
import { TenantContext } from './tenant.context';

@Injectable()
export class TenantMiddleware implements NestMiddleware {
  constructor(private readonly tenantContext: TenantContext) {}

  use(req: Request, res: Response, next: NextFunction): void {
    const tenantId = req.header('x-tenant-id');
    if (!tenantId || !/^[a-z0-9-]+$/.test(tenantId)) {
      throw new BadRequestException('Missing or invalid X-Tenant-Id');
    }

    const store = { tenantId, requestId: randomUUID() };
    // next() MUST run inside the context callback
    this.tenantContext.run(store, () => next());
  }
}

Wiring the Middleware Globally

Register the middleware in a module's configure method and apply it to all routes. Because TenantContext is injected into the middleware, both must be provided/exported from a module the app imports.

Order matters: the tenant middleware should run before anything that depends on the context (logging middleware, etc.). NestJS applies middleware in the order you chain .apply() calls and in module import order.

import { Module, NestModule, MiddlewareConsumer } from '@nestjs/common';
import { TenantContext } from './tenant.context';
import { TenantMiddleware } from './tenant.middleware';

@Module({
  providers: [TenantContext],
  exports: [TenantContext],
})
export class TenantModule implements NestModule {
  configure(consumer: MiddlewareConsumer): void {
    consumer.apply(TenantMiddleware).forRoutes('*');
  }
}

Consuming the Tenant Anywhere

Now any provider — at any depth, request-scoped or not — can inject TenantContext and read the current tenant. No @Inject(REQUEST), no request-scoped contagion, no passing tenantId through method signatures.

This is the payoff: a singleton service can safely ask for the current tenant because getStore() resolves to the right per-request store at call time.

import { Injectable } from '@nestjs/common';
import { TenantContext } from './tenant.context';

@Injectable()
export class OrderService {
  constructor(private readonly tenantContext: TenantContext) {}

  async listOrders() {
    const { tenantId } = this.tenantContext.get();
    // Every query is automatically scoped to the active tenant
    return this.repo.find({ where: { tenantId } });
  }

  // injected elsewhere
  private repo: any;
}

Scoping the Database Automatically

The biggest win is enforcing tenant isolation at the data layer instead of trusting every developer to add where tenantId = .... With the context available globally, you can centralize it:

  • Connection-per-tenant: resolve a tenant-specific datasource/connection from a pool using tenantContext.tenantId.
  • Shared schema + filter: a TypeORM/Prisma global filter or query subscriber that injects the tenant predicate.

Both approaches read the tenant from AsyncLocalStorage, so the resolver logic lives in exactly one place.

import { Injectable } from '@nestjs/common';
import { DataSource } from 'typeorm';
import { TenantContext } from './tenant.context';

@Injectable()
export class TenantConnectionProvider {
  private readonly pool = new Map<string, DataSource>();

  constructor(private readonly tenantContext: TenantContext) {}

  getDataSource(): DataSource {
    const tenantId = this.tenantContext.tenantId;
    const ds = this.pool.get(tenantId);
    if (!ds) {
      throw new Error(`No datasource initialized for tenant ${tenantId}`);
    }
    return ds;
  }
}

Middleware vs Guards vs Interceptors

Why middleware and not a guard or interceptor for opening the context?

  • Middleware runs first and wraps the entire remaining pipeline inside its next() callback — guards, interceptors, pipes, and the handler all execute within run(). This is what we want.
  • Guards/interceptors run later. An interceptor wraps the handler but not the guards that ran before it, so context opened there is partially missing.

One nuance: if you must resolve the tenant from a verified JWT, the token is validated in a guard, which runs after middleware. A common pattern is middleware to open the store and a guard/early step to populate the tenant once the JWT is verified.

Pitfalls That Break Context Propagation

AsyncLocalStorage is robust across async/await and setTimeout, but a few things silently drop the context:

  • Detached work: tasks pushed to a queue or run after the response (fire-and-forget jobs, cron triggered work) run outside the request and have no store. Capture tenantId explicitly before handing off.
  • Some pools/native callbacks that use non-promise scheduling can lose context — verify, and re-bind with als.run if needed.
  • Calling get() in app bootstrap or in a health check that bypasses the middleware throws — guard such paths or skip the middleware for them.

Rule of thumb: anything that outlives the HTTP request must be given the tenant explicitly, not via the store.

import { AsyncLocalStorage } from 'node:async_hooks';

const als = new AsyncLocalStorage<{ tenantId: string }>();
const queue: Array<() => void> = [];

function enqueueJob(work: () => void): void {
  // WRONG: read store now? It's fine here, but the job runs later/outside.
  const tenantId = als.getStore()?.tenantId; // capture explicitly
  queue.push(() => als.run({ tenantId: tenantId! }, work));
}

als.run({ tenantId: 'acme' }, () => {
  enqueueJob(() => console.log('job tenant:', als.getStore()?.tenantId));
});

// Drain later, outside the original context
queue.forEach((job) => job()); // job tenant: acme

Quick Check

You implement tenant resolution in a NestJS middleware that calls tenantContext.run(store, ...). Deep services using a singleton (default-scoped) provider read the tenant via getStore().

Rispondi nella lezione interattiva

Recap

You built implicit, leak-resistant tenant propagation:

  • Resolve early: middleware extracts and validates the tenant from header/subdomain/JWT at the request edge.
  • Propagate implicitly: wrap AsyncLocalStorage in a typed TenantContext service; call run(store, () => next()) so the whole pipeline executes inside the context.
  • Consume anywhere: any singleton provider injects TenantContext and reads the tenant — no request-scoped contagion, no threading tenantId through signatures.
  • Enforce isolation centrally at the data layer (connection-per-tenant or a global query filter).
  • Mind the boundaries: detached/queued/scheduled work loses the store — capture tenantId explicitly, and make get() throw outside a request to fail loud.
Gratis per iniziare

Impara TypeScript con un tutor IA — gratis

Scrivi ed esegui vero codice nel tuo browser, ricevi aiuto istantaneo da un tutor IA disponibile 24/7, e riprendi da dove hai lasciato sul web o nell'app.

Corsi
20
Lezioni
76
Inizia a imparare gratisVisualizza il corso completo

Domande Frequenti

La lezione «Risoluzione del tenant tramite middleware e AsyncLocalStorage» è gratuita?

Sì — il testo completo di «Risoluzione del tenant tramite middleware e AsyncLocalStorage» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso NestJS Enterprise Backend APIs, passa a CoddyKit PRO. Il corso NestJS Enterprise Backend APIs include 4 lezioni in totale.

Cosa imparerò in «Risoluzione del tenant tramite middleware e AsyncLocalStorage»?

Estragga e propaghi il tenant attivo nelle richieste usando il contesto di AsyncLocalStorage. Eserciti NestJS Enterprise Backend APIs con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.

Ho bisogno di esperienza per iniziare NestJS Enterprise Backend APIs?

Non è richiesta alcuna esperienza precedente. NestJS Enterprise Backend APIs su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 1 di 4.

Quanto tempo richiede la lezione «Risoluzione del tenant tramite middleware e AsyncLocalStorage»?

La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.

Posso scrivere ed eseguire codice in questa lezione NestJS Enterprise Backend APIs?

Sì. Ogni lezione NestJS Enterprise Backend APIs include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.

Tutte le lezioni di questo corso

  1. Risoluzione del tenant tramite middleware e AsyncLocalStorage
  2. Connessioni al database con uno schema per tenant
  3. Creazione di moduli dinamici configurabili
  4. Provider con ambito per richiesta e relativi compromessi
← Torna a NestJS Enterprise Backend APIs