Skip to main content

C# : Understanding Eager Loading, Lazy Loading, and Explicit Loading in Entity Framework


Introduction

Entity Framework, a powerful Object-Relational Mapping (ORM) tool, provides developers with various loading strategies to retrieve and work with data efficiently.

In this blog, we'll delve into three key loading techniques: Eager Loading, Lazy Loading, and Explicit Loading, each serving distinct purposes in optimizing data retrieval.

Eager Loading

Eager loading is a strategy where related data is loaded from the database along with the main entity. 

This is particularly useful when you know in advance that certain related data will be needed, helping to minimize subsequent database trips.

Let's have a look at example in Entity framework core

var employees = context.Employees
                      .Include(e => e.Department)
                      .ToList();
C#
In this example, the .Include() method ensures that the Department related to each Employee is loaded eagerly.

Lazy Loading

Lazy loading defers the loading of related data until the moment it's accessed. 

This can be advantageous in scenarios where you want to minimize the initial data retrieval and only load related entities when they are explicitly accessed.

Let's have a look at example in Entity framework core

public class Employee
{
    public int EmployeeId { get; set; }
    public string EmployeeName { get; set; }
    public int DepartmentId { get; set; }

    public virtual Department Department { get; set; }
}

// Enable lazy loading in your context
public class AppDbContext : DbContext
{
    public DbSet<Employee> Employees { get; set; }
    public DbSet<Department> Departments { get; set; }

    protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
    {
        optionsBuilder.UseLazyLoadingProxies();
    }
}

// Usage
var employee = context.Employees.First();
var departmentName = employee.Department.DepartmentName; // Lazy loading occurs here
C#
Note: Lazy loading requires proxy creation, which is enabled through .UseLazyLoadingProxies() in Entity Framework Core.

Explicit Loading

Explicit loading is a manual approach where related data is loaded on-demand, giving developers precise control over when and what data to load. 

This is beneficial in scenarios where you want to fetch related entities based on specific conditions or user interactions.

Let's have a look at example in Entity framework core

var employee = context.Employees.First();
context.Entry(employee)
       .Reference(e => e.Department)
       .Load();
C#
In this example, .Reference() is used to load a single navigation property, and .Load() triggers the explicit loading of the Department related to the specified Employee.

Conclusion

In conclusion, Choosing the appropriate loading strategy in Entity Framework is crucial for optimizing performance and minimizing unnecessary database queries. 

Eager loading is suitable when you know upfront that certain related data will be used, lazy loading defers loading until needed, and explicit loading gives you fine-grained control over data retrieval. 

By understanding and utilizing these loading techniques in your Entity Framework applications, you can strike the right balance between performance and resource efficiency.

Labels:

Comments

Post a Comment

Popular posts from this blog

Clean Architecture: What It Is and How It Differs from Microservices

In the tech world, buzzwords like   Clean Architecture   and   Microservices   often dominate discussions about building scalable, maintainable applications. But what exactly is Clean Architecture? How does it compare to Microservices? And most importantly, is it more efficient? Let’s break it all down, from understanding the core principles of Clean Architecture to comparing it with Microservices. By the end of this blog, you’ll know when to use each and why Clean Architecture might just be the silent hero your projects need. What is Clean Architecture? Clean Architecture  is a design paradigm introduced by Robert C. Martin (Uncle Bob) in his book  Clean Architecture: A Craftsman’s Guide to Software Structure and Design . It’s an evolution of layered architecture, focusing on organizing code in a way that makes it  flexible ,  testable , and  easy to maintain . Core Principles of Clean Architecture Dependency Inversion : High-level modules s...
Post a Comment
Read more

C# : How can we access private method outside class

Introduction In object-oriented programming, encapsulation is a fundamental principle that restricts direct access to the internal implementation details of a class. Private methods, being part of this internal implementation, are designed to be accessible only within the confines of the class they belong to. However, there might be scenarios where you need to access a private method from outside the class. In this blog post, we'll explore several techniques to achieve this in C#. 1. Reflection: A Powerful Yet Delicate Approach Reflection is a mechanism in C# that allows inspecting and interacting with metadata about types, fields, properties, and methods. While it provides a way to access private methods, it should be used cautiously due to its potential impact on maintainability and performance. using System ; using System . Reflection ; public class MyClass { private void PrivateMethod ( ) { Console . WriteLine ( "This is a private method."...
Post a Comment
Read more

20+ LINQ Concepts with .Net Code

LINQ   (Language Integrated Query) is one of the most powerful features in .NET, providing a unified syntax to query collections, databases, XML, and other data sources. Below are 20+ important LINQ concepts, their explanations, and code snippets to help you understand their usage. 1.  Where  (Filtering) The  Where()  method is used to filter a collection based on a given condition. var numbers = new List < int > { 1 , 2 , 3 , 4 , 5 , 6 } ; var evenNumbers = numbers . Where ( n => n % 2 == 0 ) . ToList ( ) ; // Output: [2, 4, 6] C# Copy 2.  Select  (Projection) The  Select()  method projects each element of a sequence into a new form, allowing transformation of data. var employees = new List < Employee > { /* ... */ } ; var employeeNames = employees . Select ( e => e . Name ) . ToList ( ) ; // Output: List of employee names C# Copy 3.  OrderBy  (Sorting in Ascending Order) The  Or...
Post a Comment
Read more