DTO vs entity separation benefit in Spring Boot - Performance Comparison

Performance: DTO vs entity separation benefit

MEDIUM IMPACT

This concept affects the speed of data transfer and rendering by reducing unnecessary data processing and minimizing payload size.

Sending data from backend to frontend efficiently

Spring Boot

public class UserDTO {
  private String username;
  private String email;
  // getters and setters
}

// Map UserEntity to UserDTO and return DTO in API response

Only necessary fields are sent, reducing payload size and avoiding sensitive data exposure.

📈 Performance GainReduces payload size by 20-30%, speeds up JSON parsing and rendering

Sending data from backend to frontend efficiently

Spring Boot

public class UserEntity {
  private Long id;
  private String username;
  private String password;
  private String email;
  private Date createdAt;
  // getters and setters
}

// Returning UserEntity directly in API response

Sending full entity exposes sensitive data and sends unnecessary fields, increasing payload size and processing time.

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

Performance Comparison

Pattern	Payload Size	JSON Parsing Time	Rendering Delay	Verdict
Entity sent directly	Large (includes all fields)	High (more data to parse)	Longer (delays LCP)	[X] Bad
DTO sent	Smaller (only needed fields)	Low (less data to parse)	Shorter (faster LCP)	[OK] Good

Rendering Pipeline

When DTOs are used, the backend sends smaller JSON payloads. The browser parses less data, reducing time spent in scripting and rendering stages.

→Data Transfer

→Scripting (JSON parsing)

→Rendering

⚠️ BottleneckScripting (JSON parsing) due to large payloads

Core Web Vital Affected

LCP

This concept affects the speed of data transfer and rendering by reducing unnecessary data processing and minimizing payload size.

Optimization Tips

1Always send only necessary data to reduce payload size.

2Avoid exposing sensitive or unused fields by separating DTOs from entities.

3Smaller JSON payloads speed up parsing and improve Largest Contentful Paint.

Performance Quiz - 3 Questions

What is the main performance benefit of using DTOs instead of entities in API responses?

A DTOs increase server CPU usage

B Entities load faster because they have more data

C Smaller payload size reduces JSON parsing and speeds up rendering

D DTOs cause more network requests

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, select API response, check size of JSON payload.

What to look for: Smaller payload size and faster load times indicate good DTO usage.