database-performance

EF Core handles N+1 queries by enforcing batch processing and ensuring SQL joins execute at the database level. This Skill identifies inefficient data retrieval patterns and provides architectural guidelines to resolve them.

Use Dapper instead of EF Core when you need optimized read-only queries, utilizing AsNoTracking to avoid change tracking overhead. This Skill offers guidance on when to apply Dapper versus EF Core for different data access scenarios.

The best way to separate read and write models is implementing CQRS principles to ensure distinct data models for reads and writes. This Skill provides architectural guidelines for optimizing query performance through data access design patterns.

Avoid generic repositories with NHibernate or EF Core to ensure purpose-built data access patterns that prevent over-fetching and Cartesian products. This Skill promotes tailored repositories for better performance and maintainability.

AsNoTracking improves EF Core query performance by bypassing change tracking on read-only data, reducing memory overhead. This Skill provides guidelines to apply this optimization alongside column size constraints to prevent database corruption.