Request DTO for input in Spring Boot - Step-by-Step Execution

Concept Flow - Request DTO for input

Client sends HTTP request

↓

Spring Boot Controller receives request

↓

Request body parsed into DTO object

↓

Controller method uses DTO for processing

↓

Response generated and sent back

The client sends data in a request, Spring Boot converts it into a DTO object, which the controller uses to process the input.

Execution Sample

Spring Boot

public record UserRequestDTO(String name, int age) {}

@PostMapping("/user")
public ResponseEntity<String> addUser(@RequestBody UserRequestDTO user) {
    return ResponseEntity.ok("User " + user.name() + " added");
}

This code defines a DTO to receive user data and a controller method that accepts it from the request body.

Execution Table

Step	Action	Input Data	DTO State	Controller Output
1	Receive HTTP POST /user	{"name":"Alice","age":30}	null	null
2	Parse JSON to DTO	{"name":"Alice","age":30}	UserRequestDTO[name=Alice, age=30]	null
3	Call controller method with DTO	UserRequestDTO[name=Alice, age=30]	UserRequestDTO[name=Alice, age=30]	null
4	Process DTO and create response	UserRequestDTO[name=Alice, age=30]	UserRequestDTO[name=Alice, age=30]	"User Alice added"
5	Send HTTP response	null	UserRequestDTO[name=Alice, age=30]	"User Alice added"

💡 Request processed and response sent back to client

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
user	null	UserRequestDTO[name=Alice, age=30]	UserRequestDTO[name=Alice, age=30]	UserRequestDTO[name=Alice, age=30]
response	null	null	null	"User Alice added"

Key Moments - 2 Insights

Why does the controller method parameter have @RequestBody annotation?

The @RequestBody tells Spring Boot to convert the incoming JSON into the DTO object before calling the method, as shown in execution_table step 2.

What happens if the JSON keys don't match DTO fields?

Spring Boot will fail to map those fields, and the DTO fields will be null or default, causing possible errors. This is seen in step 2 where parsing sets the DTO state.

Visual Quiz - 3 Questions

Look at the execution_table, what is the DTO state after step 2?

A UserRequestDTO[name=Bob, age=25]

B null

C UserRequestDTO[name=Alice, age=30]

D Empty DTO object

💡 Hint

Check the 'DTO State' column in row for step 2 in execution_table

At which step does the controller method receive the DTO object?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at the 'Action' column describing method call in execution_table

If the input JSON was missing the 'age' field, how would the DTO state change after step 2?

A DTO would have age=0 (default int value)

B DTO would have age=null

C Parsing would fail and DTO would be null

D DTO would have age=some random value

💡 Hint

Primitive int fields default to 0 if missing in JSON, as per Java behavior

Concept Snapshot

Request DTO in Spring Boot:
- Define a record or class with fields for input data
- Use @RequestBody in controller method parameter
- Spring Boot auto-converts JSON to DTO
- Controller uses DTO to process input
- Response sent back after processing

Full Transcript

In Spring Boot, when a client sends data in an HTTP request, the controller can receive this data as a Request DTO. The DTO is a simple object or record that holds the input fields. The @RequestBody annotation tells Spring Boot to convert the JSON request body into this DTO object automatically. The controller method then uses this DTO to process the input and generate a response. This flow ensures clean separation of input data and business logic.