Projections for Data Minimization

Project entities into DTOs to reduce data transfer overhead and database CPU usage.

In this lesson, you will learn how to optimize your application’s performance by using LINQ projections to fetch only the data you truly need from the database.

The Problem: Over-Fetching

When you query an entity directly—for example, context.Users.ToList()—Entity Framework generates a SELECT * statement. This pulls every single column from the database table, including large text fields or binary data you might not be using in that specific view. This wastes database CPU cycles, increases memory pressure on your application, and slows down network transfer.

The Solution: Projections

A projection allows you to transform your database entities into a specialized Data Transfer Object (DTO) at the database level. By using the .Select() operator in your LINQ query, EF Core translates your request into a targeted SELECT statement that fetches only the specific columns required to populate your object.

Consider this example where we only need the user's name and email:

// Instead of fetching the entire User entity
var userSummaries = context.Users
    .Select(u => new UserSummaryDto 
    {
        FullName = u.FirstName + " " + u.LastName,
        Email = u.Email
    })
    .ToList();

Because this projection happens within the IQueryable expression tree, EF Core translates this into SQL that requests only the FirstName, LastName, and Email columns. The database engine does less work scanning rows, and your application receives a much smaller payload.

Why This Matters

Projections are one of the most effective ways to reduce data transfer overhead. By projecting into a lightweight DTO, you avoid loading unnecessary navigation properties or large blobs that aren't relevant to the current operation. This is especially vital when dealing with wide tables or frequently accessed lists where performance bottlenecks often originate from fetching "fat" entities when only "slim" data is required.

Key Takeaway: Use projections to map your entities into DTOs at the query level, ensuring the database only retrieves the specific columns necessary for your current task.