Database Performance · Aaronontheweb/dotnet-skills
Design high-performance database access patterns
Guides database access design: separate read and write models, avoid N+1 queries, use AsNoTracking, cap row counts, and keep joins in SQL rather than application code. Useful when designing a new data layer or fixing slow EF Core or Dapper queries.
Good for
- Design a read/write-separated data access layer
- Diagnose N+1 query performance problems
- Choose between EF Core and Dapper for a project
- Source repository
- Aaronontheweb/dotnet-skills
- Category
- Coding
Open-source skills are maintained by their authors and listed as published, with attribution. Results depend on how well the skill fits your task and material.
A good place to start
Review this EF Core query and tell me how to fix its performance issues.
Make your next great thing.
Bring a question, a file, or an idea that’s not quite there yet.