domains / families / data / database-performance

database-performance

separate

Database access patterns for performance. Separate read/write models, avoid N+1 queries, use AsNoTracking, apply row limits, and never do application-side joins. Works with EF Core and Dapper.

When to use

• Designing data access layers
• Optimizing slow database queries
• Choosing between EF Core and Dapper
• Avoiding common performance pitfalls
• | Scenario | Recommendation | |----------|---------------| | Simple CRUD | EF Core | | Complex read queries | Dapper | | Writes with validation | EF Core | | Bulk operations | Dapper or raw SQL | | Reporting/analytics | Dapper | | Domain-h…

Skill page

Source