entityframework-dotnet-single-db

Configure a shared multi-tenant EF Core database by registering a generic AppDbContext with a fixed connection string and implementing global query filters to scope data access via tenant identifiers. This approach simplifies DI registration without complex interceptors.

Automatic tenant data filtering in EF Core uses global query filters on ITenantEntity instances to restrict data access based on current tenant identifiers. These identifiers are extracted from the X-Tenant-Id header, claims, query parameters, or host values.

Use a shared single database for small to medium SaaS scenarios where operational simplicity is prioritized over strict database isolation. This model eliminates the overhead of managing separate databases per tenant while maintaining data segregation through query filtering.

Register an AppDbContext with a fixed connection string by using simplified dependency injection setup. This registers a single generic database context for the entire SaaS application, removing the need for complex interceptor configurations during initialization.

The limitation of a shared database architecture for multi-tenant SaaS is the lack of per-tenant database isolation. This approach prioritizes operational simplicity and is suitable for small to medium scenarios, but may not meet strict data isolation requirements for larger enterprise tenants.

Yes, you can filter data in EF Core using tenant identifiers extracted from HTTP headers like X-Tenant-Id. The framework also supports resolving tenant context from claims, query parameters, or host values to automatically apply global query filters.