Architecture · hard

48. Multi-Tenancy Patterns

Serving multiple tenants from one codebase.

Multi-tenancy in Laravel is commonly implemented via single-database (a tenant_id column plus global query scopes) or multi-database (separate database connections per tenant, switched dynamically) approaches. Packages like stancl/tenancy automate database switching, domain-based tenant identification, and per-tenant migrations/queues. Careful attention is needed so background jobs, cached data, and file storage paths remain properly scoped to the correct tenant.

Check your understanding

1. What is a common single-database multi-tenancy technique?
Separate servers per tenantA tenant_id column with global scopes filtering queriesNo isolation at allStoring tenants in cookies only
2. What extra care is needed for queued jobs in a multi-tenant app?
None, jobs are tenant-agnostic by defaultEnsuring the job serializes and restores the correct tenant context when processedJobs must run synchronously onlyTenants can't use queues