Entity to DTO mapping in Spring Boot - Performance & Optimization

Performance: Entity to DTO mapping

MEDIUM IMPACT

This affects the server response time and the size of data sent to the client, impacting page load speed and interaction responsiveness.

Mapping database entities directly to API responses

Spring Boot

public List<UserDTO> getUsers() {
    return userRepository.findAll().stream()
        .map(user -> new UserDTO(user.getId(), user.getName()))
        .collect(Collectors.toList());
}

Sends only required fields, reducing payload size and improving serialization speed.

📈 Performance GainReduces payload size by up to 50%, speeds up JSON serialization and client rendering

Mapping database entities directly to API responses

Spring Boot

public List<User> getUsers() {
    return userRepository.findAll();
}

Returns full entity objects including unnecessary fields, increasing payload size and exposing internal data.

📉 Performance CostIncreases payload size by 20-50%, blocks rendering longer due to larger JSON parsing

Performance Comparison

Pattern	CPU Overhead	Payload Size	Serialization Time	Verdict
Direct entity return	Low	High	High	[X] Bad
Manual DTO mapping	Medium	Medium	Medium	[!] OK
Library-based DTO mapping	Low	Low	Low	[OK] Good
DTO with nested full collections	High	Very High	Very High	[X] Bad
DTO with summary fields only	Low	Low	Low	[OK] Good

Rendering Pipeline

Entity to DTO mapping affects the server-side serialization stage before data is sent to the browser, impacting how quickly the browser can start rendering content.

→Server Processing

→Network Transfer

→Browser Parsing

⚠️ BottleneckServer Processing due to inefficient mapping and large payload serialization

Core Web Vital Affected

LCP

This affects the server response time and the size of data sent to the client, impacting page load speed and interaction responsiveness.

Optimization Tips

1Always map entities to DTOs to send only necessary data.

2Avoid eager mapping of large nested collections in DTOs.

3Use mapping libraries to improve performance and maintainability.

Performance Quiz - 3 Questions

What is a main performance benefit of using DTOs instead of returning entities directly?

A More complex code improves security

B Smaller payload size reduces load time

C Entities are faster to serialize

D DTOs increase server CPU usage

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, click on API response, and inspect the size and content of JSON payload.

What to look for: Look for large payload sizes and long waiting times indicating heavy or inefficient data transfer.

Practice

1. What is the main purpose of mapping an Entity to a DTO in Spring Boot?

easy

A. To speed up database queries

B. To separate database structure from data sent to clients

C. To store data in a different database

D. To automatically generate database tables

Solution

1. Step 1: Understand Entity and DTO roles

   Entity represents database data, DTO is for data transfer outside the app.

2. Step 2: Identify the purpose of mapping

   Mapping hides database details and controls what data is sent to clients.

3. Final Answer:

   To separate database structure from data sent to clients -> Option B

4. Quick Check:

   Entity to DTO mapping = data separation [OK]

Hint: Think: Entity is internal, DTO is external data format [OK]

Common Mistakes:

• Confusing DTO with database storage
• Thinking mapping speeds up queries
• Assuming DTO changes database schema

2. Which of the following is the correct way to manually map an Entity field name to a DTO field fullName in Java?

easy

A. entity.getName(dto.setFullName());

B. entity.setName(dto.getFullName());

C. dto.getFullName(entity.setName());

D. dto.setFullName(entity.getName());

Solution

1. Step 1: Identify source and target objects

   Entity is source, DTO is target for mapping.

2. Step 2: Use getter on entity and setter on DTO

   Correct syntax is calling entity.getName() and passing to dto.setFullName().

3. Final Answer:

   dto.setFullName(entity.getName()); -> Option D

4. Quick Check:

   Getter from entity, setter on DTO [OK]

Hint: Getter from entity, setter on DTO for mapping [OK]

Common Mistakes:

• Reversing source and target in mapping
• Using setter as getter or vice versa
• Calling methods with wrong parameters

3. Given the following code snippet, what will be the output of dto.getAge() after mapping?

public class UserEntity {
  private int age = 30;
  public int getAge() { return age; }
}

public class UserDTO {
  private int age;
  public void setAge(int age) { this.age = age; }
  public int getAge() { return age; }
}

UserEntity entity = new UserEntity();
UserDTO dto = new UserDTO();
dto.setAge(entity.getAge());
System.out.println(dto.getAge());

medium

A. 30

B. 0

C. null

D. Compilation error

Solution

1. Step 1: Check initial value in Entity

   Entity's age is set to 30 by default.

2. Step 2: Map Entity age to DTO and print

   DTO's age is set to entity.getAge(), so dto.getAge() returns 30.

3. Final Answer:

   30 -> Option A

4. Quick Check:

   Entity age 30 mapped to DTO age 30 [OK]

Hint: Mapping copies values exactly unless changed [OK]

Common Mistakes:

• Assuming default int is null
• Confusing getter/setter roles
• Expecting compilation error without syntax issues

4. Identify the error in this manual mapping method:

public UserDTO mapToDTO(UserEntity entity) {
  UserDTO dto = new UserDTO();
  dto.setName(entity.getFullName());
  dto.setEmail(entity.getEmail());
  return dto;
}

Assuming UserEntity has a getName() method but no getFullName() method.

medium

A. Setter methods used incorrectly

B. Missing return statement

C. Calling non-existent method getFullName() on entity

D. DTO object not created

Solution

1. Step 1: Check entity methods used

   Code calls entity.getFullName(), but entity only has getName().

2. Step 2: Identify cause of error

   Calling a method that does not exist causes a compile-time error.

3. Final Answer:

   Calling non-existent method getFullName() on entity -> Option C

4. Quick Check:

   Method must exist on entity for mapping [OK]

Hint: Verify entity methods before calling in mapping [OK]

Common Mistakes:

• Assuming method names match automatically
• Ignoring compile errors from wrong method calls
• Confusing getter names between classes

5. You want to map a list of UserEntity objects to a list of UserDTO objects using Java streams in Spring Boot. Which code snippet correctly performs this mapping assuming a method mapToDTO(UserEntity entity) exists?

hard

A. List<UserDTO> dtos = entities.stream().map(this::mapToDTO).collect(Collectors.toList());

B. List<UserDTO> dtos = entities.map(entity -> mapToDTO(entity));

C. List<UserDTO> dtos = entities.forEach(entity -> mapToDTO(entity));

D. List<UserDTO> dtos = entities.stream().forEach(this::mapToDTO);

Solution

1. Step 1: Use stream() to process list

   entities.stream() creates a stream to transform elements.

2. Step 2: Use map() to convert each entity to DTO

   map(this::mapToDTO) applies the mapping method to each element.

3. Step 3: Collect results into a list

   collect(Collectors.toList()) gathers mapped DTOs into a list.

4. Final Answer:

   List<UserDTO> dtos = entities.stream().map(this::mapToDTO).collect(Collectors.toList()); -> Option A

5. Quick Check:

   Stream map + collect to list = correct mapping [OK]

Hint: Use stream().map(...).collect(toList()) for list mapping [OK]

Common Mistakes:

• Using forEach instead of map for transformation
• Calling map on list directly without stream()
• Not collecting results after mapping