title: Lazy Loading vs Eager Loading
body: <p>Under what situation could eager loading be more beneficial than lazy loading?</p>
  <p>Lazy loading in Entity Framework is the default phenomenon that happens for loading and accessing the related entities. However, eager loading is referred to the practice of force-loading all these relations.</p>
  <p>I'm asking this, because it is obvious that lazy loading is more resource-friendly, and even if we use the <code>ToList()</code> method, we can still take advantage of the lazy loading behavior.</p>
  <p>However, I thought maybe lazy loading increases the number of requests to the actual database and maybe that's why sometimes developers use the <code>Inlcude</code> method to force-loading all relations.</p>
  <p>For example, when using the Visual Studio auto-scaffolding in MVC 5, the Index method automatically created in the controller always uses Eager Loading, and I've always had the question of why Microsoft uses Eager Loading default in that case.</p>
  <p>I would appreciate it if someone explains to me under what situation eager loading would be more beneficial than lazy loading, and why do we use it at all while there's something more resource-friendly as Lazy Loading?</p>