linq-optimization-patterns

N+1 queries occur when fetching a parent entity triggers separate queries for each related child. Eliminate this by using eager loading with `Include`/`ThenInclude`, projections via `Select`, or batch loading to fetch all data in one or few round-trips instead of sequential queries.

Apply LINQ optimization patterns: use `AsNoTracking` for read-only scenarios, `AsSplitQuery` to prevent Cartesian explosion with multiple collections, and projections to select only needed columns. These reduce database load and improve response times from seconds to milliseconds.

Yes. Combine `Include`/`ThenInclude` for eager loading with `Select` projections to fetch and shape related data efficiently. Use `WhereIf` for dynamic filtering, and apply `AsNoTracking` when changes aren't needed, creating performant queries for complex navigations and DTO projections.

Implement cursor-based or optimized offset pagination to avoid loading unnecessary rows. Use ABP's `WhereIf` extension for conditional filtering without building separate queries. Combine with `Select` projections and `AsNoTracking` to minimize database round-trips and memory overhead.

Use `AsSplitQuery` when loading multiple collections causes Cartesian explosion—where result sets multiply unexpectedly. It executes separate queries per collection instead of one large join, maintaining performance while keeping code readable with Include syntax.

Yes. These LINQ and EF Core patterns are applied directly to ABP data-access layers. ABP integration includes support for `WhereIf` dynamic filtering, Include eager loading, and projection-based queries, enabling fast, responsive endpoints with minimal database load.