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.

Comments

Popular posts from this blog

Implementing and Integrating RabbitMQ in .NET Core Application: Shopping Cart and Order API

RabbitMQ is a robust message broker that enables communication between services in a decoupled, reliable manner. In this guide, we’ll implement RabbitMQ in a .NET Core application to connect two microservices: Shopping Cart API (Producer) and Order API (Consumer). 1. Prerequisites Install RabbitMQ locally or on a server. Default Management UI: http://localhost:15672 Default Credentials: guest/guest Install the RabbitMQ.Client package for .NET: dotnet add package RabbitMQ.Client 2. Architecture Overview Shopping Cart API (Producer): Sends a message when a user places an order. RabbitMQ : Acts as the broker to hold the message. Order API (Consumer): Receives the message and processes the order. 3. RabbitMQ Producer: Shopping Cart API Step 1: Install RabbitMQ.Client Ensure the RabbitMQ client library is installed: dotnet add package RabbitMQ.Client Step 2: Create the Producer Service Add a RabbitMQProducer class to send messages. RabbitMQProducer.cs : using RabbitMQ.Client; usin...

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...

How Does My .NET Core Application Build Once and Run Everywhere?

One of the most powerful features of .NET Core is its cross-platform nature. Unlike the traditional .NET Framework, which was limited to Windows, .NET Core allows you to build your application once and run it on Windows , Linux , or macOS . This makes it an excellent choice for modern, scalable, and portable applications. In this blog, we’ll explore how .NET Core achieves this, the underlying architecture, and how you can leverage it to make your applications truly cross-platform. Key Features of .NET Core for Cross-Platform Development Platform Independence : .NET Core Runtime is available for multiple platforms (Windows, Linux, macOS). Applications can run seamlessly without platform-specific adjustments. Build Once, Run Anywhere : Compile your code once and deploy it on any OS with minimal effort. Self-Contained Deployment : .NET Core apps can include the runtime in the deployment package, making them independent of the host system's installed runtime. Standardized Libraries ...