database-performance

SKILL.md

Read and write models are fundamentally different - they have different shapes, columns, and purposes. Don't create a single "User" entity and reuse it everywhere.

Never return unbounded result sets. Every read method should have a configurable limit.

EF Core's change tracking is expensive. Disable it for read-only queries.

Patrones de acceso a la base de datos para el rendimiento. Separe los modelos de lectura/escritura, evite consultas N+1, use AsNoTracking, aplique límites de filas y nunca realice uniones del lado de la aplicación. Funciona con EF Core y Dapper. Fuente: aaronontheweb/dotnet-skills.

Ver original