Do y'all generally use lazy loading while working with entity framewor

The Lazy Loading means the related entities are loaded transparently when the navigation property is accessed. in other words, in the underlying of Entity Framework, the Lazy Loading would run separate SQL queries.

In the blowing scenario, the Lazy Loading would be a no sense option. you have many books, each book has navigation properties like author, reviewer, editor. you are iterating books to access these navigation properties. Lazy Loading is going to degrade the performance because books are small lightweight data. for example, if you have 5 thousand books, each iteration will access 3 navigation properties, then you are going to execute 15 thousand separate SQL queries. it would be a disaster!

Actually. The Lazy Loading was added on .NET, it’s not a wise choice for most scenarios. but if you have a member that could be costly to load, and this member is infrequently visited, for scenarios like this, it would be a good choice to use Lazy Loading.

 

I liked the above example. Check this blog for better analysis:

Analysis of advantage and disadvantage of Eager Loading, Explicit Loading, Lazy Loading

https://blog.davidwu.xyz/csharp-ef/2020/03/21/Analysis-of-advantage-and-disadvantage-of-Eager-Explicit-Lazy-Loading/ 

It is a thumb rule that in Web applications the data must available ahead of time , if it is a desktop app then doesn't matter but for web , no , never load related data on just in time , so avoid lazy loading as much you can,

also microsoft documentation has a lot of examples of loading related data which are not quite good for performance , just because it is written in MS docx doesn't mean it is bullet correct.