Thread by @mwaseemzakir

💡Tracking vs Non Tracking Queries in .NET
1) Tracking Queries
2) Non Tracking Queries
3) Identity Resolution
4) How to set tracking by default for context🧵🔽
#dotnet

𝐓𝐫𝐚𝐜𝐤𝐢𝐧𝐠 : By default all queries are tracked , so behind the seen a change tracker keeps working on each entity. If you want to perform Update/Delete then you should use tracking.
#dotnet

𝐍𝐨𝐧 𝐓𝐫𝐚𝐜𝐤𝐢𝐧𝐠 : If you just need read only data then you don't need your queries to keep tracking of change , you can simply go with no tracking and help the query run more speedy.
#dotnet

𝐈𝐝𝐞𝐧𝐭𝐢𝐭𝐲 𝐑𝐞𝐬𝐨𝐥𝐮𝐭𝐢𝐨𝐧 : When you use a tracking query in Entity Framework Core, it uses identity resolution to return the same entity instance from the change tracker if it's already being tracked.
#dotnet

However, a no-tracking query doesn't use the change tracker and always returns a new instance of the entity, even if the same entity is contained in the result multiple times

#dotnet

To combine both behaviors, EF Core has added AsNoTrackingWithIdentityResolution(), which uses a stand-alone change tracker to do identity resolution without tracking the results in the context.

Once the query is enumerated, the change tracker is garbage collected

#dotnet

✉ Join my weekly .NET Newsletter with 700+ Software Engineers here : lnkd.in/dcvY9jEE

#dotnet