This article outlines five EF Core query patterns behind many slow pages, plus one habit that catches them all: read the SQL EF generates instead of judging the C# code. It covers N+1 queries, loading whole tables or unneeded columns, cartesian explosions from collection Includes, and filters that prevent index use. It is a practical checklist for anyone writing data access code.
The author shows a multi-tenancy pattern for ASP.NET Core and EF Core that uses global query filters so each request only sees its own tenant's rows. When no tenant is set, filtered queries return nothing, which fails closed. The post also covers tenant-scoped unique indexes, limiting IgnoreQueryFilters(), and an integration test that checks cross-tenant access. It is a practical starting point for SaaS backends.
A developer moving from Spring Boot to EF Core explains how SQL Server's rowversion differs from JPA's @version field. The value comes from a database-wide counter, so it is not a per-row version number. This matters for .NET developers who need to set up optimistic concurrency correctly.