efcore-patterns

Improve EF Core read performance by configuring NoTracking as the default behavior, which disables change tracking for queries unless explicitly required for updates. This reduces memory overhead and speeds up data retrieval.

Avoid cartesian explosion in Entity Framework Core by enabling query splitting behavior. This approach loads multiple collections in separate SQL queries rather than joining them, preventing massive intermediate result sets and boosting performance.

Run scalable bulk updates in EF Core using ExecuteUpdate and ExecuteDelete operations. These methods execute directly against the database to modify or delete records without loading entities into the change tracker, ensuring high performance.

Manage EF Core migrations safely through dedicated services and CLI workflows. Establishing a dedicated migration runner separates migration execution from application startup, preventing schema drift and ensuring reliable database evolution.

Entity Framework Core applications fail during transient connection drops if they lack resilient execution strategies. Implementing a retry policy handles these temporary failures automatically, stabilizing data access operations.

Yes, you can apply EF Core query splitting to existing domain models. Configuring this behavior optimizes read paths by loading multiple collections efficiently, directly addressing performance degradation without altering the underlying data structure.