vendix-backend-middleware

Configure multi-tenant middleware in NestJS by applying DomainResolverMiddleware globally to intercept requests, resolve subdomains, and inject tenant identifiers into the request context. This automates wiring for dynamic domain detection without manual route handlers.

Domain resolution caching uses an LRU cache to store resolved domains, minimizing Prisma database lookups for frequent subdomain requests. This reduces database load by serving cached tenant identifiers like store_id and organization_id directly from memory.

Yes, the middleware injects store_id, organization_id, and domain_type into the request-scoped context. This exposes tenant identifiers to NestJS controllers and services, enabling Prisma queries scoped to the specific store or organization making the request.

The best way to detect domains is using middleware that parses the request host to identify store, organization, or vendix_core domains. It automatically categorizes the domain type and injects the corresponding tenant IDs into the request context.

Yes, Prisma integration is required because the middleware relies on Prisma to perform initial database lookups for domain resolutions. Resolved tenant identifiers are cached in an LRU cache to minimize repeated Prisma queries for subsequent requests.