data-database-performance

What problem does it solve?

This Skill blends proven data-access patterns to dramatically improve query performance by separating read models from write models, minimizing unnecessary tracking and data transfer.

Core Features & Use Cases

• Separate read and write models to optimize queries and commands.
• Enforce always-limited result sets with explicit pagination.
• Use AsNoTracking for reads to avoid unnecessary change tracking overhead.
• Avoid N+1 queries by embracing joins in SQL or batched reads.
• Choose EF Core for writes and Dapper for reads to balance productivity and performance.

Quick Start

Create a pair of read/write stores per aggregate, wire them to your DbContext or data layer, enable AsNoTracking on read queries, and implement a paginated Get methods with a fixed limit.