Getting the best out of Entity Framework Core
summary
Explains how EF Core translates LINQ into SQL, how relational fix‑up and change tracking produce four books and three authors in memory from one query, and why EF Core 3’s AsNoTracking change and rewrite of LINQ→SQL break and speed up some queries. Shows select loading with AutoMapper ProjectTo to do averages in the database, using SQLite/SQL Server for unit tests, and a real case that cuts a page load from nine seconds to under two. Notes Cosmos DB limitations and soft‑delete query filters.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:15Entity Framework Core in Action
- 1:58A super-simple database to show how EF Core works
- 9:29Three types of relationships
- 12:34Three (four) ways of reading the database
- 15:15A look at the Select load code
- 18:16The SQL created by the Select query
- 23:56A better way to set up the relationships
- 26:54EF Core works out the correct order for the SQL
- 29:30Understanding relational fixup
- 31:09Relational fixup and hierarchical data
- 33:45EF Core and Domain-Driven Design in 5 minutes
- 35:39An example of a DDD-styled entity class
- 37:44Alternative to Delete - soft delete
- 41:23ValueConversions (came in EF Core 2.1)
- 43:00Using code to configure EF Core
- 45:25Using Cosmos DB to improve performance
- 46:52Cosmos DB-in EF Core 3 (some limitations)
- 48:33Unit testing applications that user EF Core
- 53:37The end
related talks
01h 04mCommon mistakes in EF Core
56mEntity Framework debugging using SQL Server: A Detective Story
01h 05mCommon mistakes in EF Core
01h 01mEntity Framework Core Unchained Getting the Best Performance from Your ORM
49mHow Entity Framework translates LINQ all the way to SQL
01h 01m10 things you didn't know EF Core can do
01h 04mCommon mistakes in EF Core
47mEF Core 6: Working on the Bucket List