@RequestBody for JSON input in Spring Boot - Performance & Optimization

Performance: @RequestBody for JSON input

MEDIUM IMPACT

This affects the server-side processing time and the responsiveness of the API endpoint when receiving JSON data.

Handling JSON input in a Spring Boot REST controller

Spring Boot

@PostMapping("/data")
public ResponseEntity<String> receiveData(@RequestBody Data data) {
    // Spring automatically parses JSON to Data object
    // process data
    return ResponseEntity.ok("Received");
}

Spring handles JSON parsing efficiently using HttpMessageConverters, reducing manual overhead.

📈 Performance GainFaster request processing; reduces CPU usage and improves API responsiveness.

Handling JSON input in a Spring Boot REST controller

Spring Boot

@PostMapping("/data")
public ResponseEntity<String> receiveData(@RequestBody String json) throws IOException {
    // Manually parse JSON string
    ObjectMapper mapper = new ObjectMapper();
    Data data = mapper.readValue(json, Data.class);
    // process data
    return ResponseEntity.ok("Received");
}

Manually parsing JSON string causes extra processing and error-prone code, increasing latency.

📉 Performance CostBlocks request handling longer due to manual parsing; adds CPU overhead per request.

Performance Comparison

Pattern	CPU Usage	Parsing Overhead	Latency Impact	Verdict
Manual JSON parsing in controller	High	High	Increases latency	[X] Bad
@RequestBody automatic JSON binding	Low	Low	Minimal latency impact	[OK] Good

Rendering Pipeline

When a JSON request arrives, Spring's DispatcherServlet routes it to the controller. The @RequestBody annotation triggers HttpMessageConverter to parse JSON into Java objects before controller logic runs.

→Server Request Parsing

→Controller Method Execution

⚠️ BottleneckJSON deserialization in HttpMessageConverter can be CPU intensive if inefficient or large payloads.

Core Web Vital Affected

INP

This affects the server-side processing time and the responsiveness of the API endpoint when receiving JSON data.

Optimization Tips

1Use @RequestBody to let Spring handle JSON parsing automatically.

2Avoid manual JSON parsing in controller methods to reduce CPU overhead.

3Validate and limit JSON payload size to prevent high latency.

Performance Quiz - 3 Questions

What is the main performance benefit of using @RequestBody for JSON input in Spring Boot?

A It compresses JSON data before sending to server.

B It caches JSON data on the client side.

C Spring automatically parses JSON, reducing manual CPU overhead.

D It delays JSON parsing until after controller execution.

DevTools: Network

How to check: Open DevTools, go to Network tab, send JSON POST request, and check request payload size and response time.

What to look for: Look for fast response times and no excessive delays in server processing indicating efficient JSON handling.

Practice

1. What is the main purpose of the @RequestBody annotation in a Spring Boot controller?

easy

A. To validate form data submitted via GET requests

B. To send JSON data back in the HTTP response

C. To map URL query parameters to method arguments

D. To automatically convert JSON from the HTTP request body into a Java object

Solution

1. Step 1: Understand the role of @RequestBody

   @RequestBody tells Spring Boot to take JSON data sent in the HTTP request body and convert it into a Java object automatically.

2. Step 2: Differentiate from other annotations

   It does not handle response data (that's @ResponseBody), nor does it map query parameters or validate GET form data.

3. Final Answer:

   To automatically convert JSON from the HTTP request body into a Java object -> Option D

4. Quick Check:

   @RequestBody = JSON to Java object [OK]

Hint: Remember: @RequestBody reads JSON input from request body [OK]

Common Mistakes:

• Confusing @RequestBody with @ResponseBody
• Thinking it maps URL parameters
• Assuming it validates data automatically

2. Which of the following method signatures correctly uses @RequestBody to accept a JSON object representing a User in a Spring Boot controller?

easy

A. public ResponseEntity<String> addUser(@RequestBody User user)

B. public ResponseEntity<String> addUser(@RequestParam User user)

C. public ResponseEntity<String> addUser(@PathVariable User user)

D. public ResponseEntity<String> addUser(User user)

Solution

1. Step 1: Identify correct annotation for JSON body

   @RequestBody is required to tell Spring Boot to convert JSON in the request body to a User object.

2. Step 2: Check other annotations

   @RequestParam reads query parameters, @PathVariable reads URL path segments, and no annotation means no automatic JSON conversion.

3. Final Answer:

   public ResponseEntity<String> addUser(@RequestBody User user) -> Option A

4. Quick Check:

   JSON input needs @RequestBody [OK]

Hint: Use @RequestBody for JSON input, not @RequestParam or @PathVariable [OK]

Common Mistakes:

• Using @RequestParam instead of @RequestBody
• Forgetting @RequestBody annotation
• Confusing @PathVariable with JSON input

3. Given the following controller method:

  @PostMapping("/add")
  public String addUser(@RequestBody User user) {
    return "Hello " + user.getName();
  }

And the JSON sent in the request body is:

{"name": "Alice"}

What will be the response?

medium

A. HTTP 400 Bad Request

B. "Hello null"

C. "Hello Alice"

D. Compilation error

Solution

1. Step 1: Understand JSON to Java object mapping

   The JSON {"name": "Alice"} maps to a User object with name set to "Alice".

2. Step 2: Check method return value

   The method returns "Hello " + user.getName(), so it returns "Hello Alice".

3. Final Answer:

   "Hello Alice" -> Option C

4. Quick Check:

   JSON name maps to user.getName() = "Hello Alice" [OK]

Hint: JSON keys map to object fields, so output uses those values [OK]

Common Mistakes:

• Assuming user.getName() is null
• Expecting HTTP error without malformed JSON
• Confusing request body with query parameters

4. Consider this controller method:

@PostMapping("/user")
public String createUser(@RequestBody User user) {
  return user.getEmail();
}

If the client sends an empty request body, what will happen?

medium

A. Spring Boot throws an HTTP 400 Bad Request error

B. The method returns null

C. The method returns an empty string

D. Compilation error due to missing @RequestBody

Solution

1. Step 1: Check behavior with empty JSON body

   When @RequestBody expects JSON but receives empty body, Spring Boot cannot create the User object.

2. Step 2: Understand Spring Boot error handling

   Spring Boot responds with HTTP 400 Bad Request for missing or malformed JSON input.

3. Final Answer:

   Spring Boot throws an HTTP 400 Bad Request error -> Option A

4. Quick Check:

   Empty JSON body causes HTTP 400 error [OK]

Hint: Empty JSON body with @RequestBody causes HTTP 400 error [OK]

Common Mistakes:

• Assuming method returns null or empty string
• Thinking compilation error occurs
• Ignoring HTTP error on missing JSON

5. You want to create a Spring Boot REST endpoint that accepts a JSON array of User objects in the request body and returns the count of users received. Which method signature correctly uses @RequestBody to achieve this?

hard

A. public int countUsers(@RequestBody User user)

B. public int countUsers(@RequestBody List<User> users)

C. public int countUsers(@RequestParam List<User> users)

D. public int countUsers(@PathVariable List<User> users)

Solution

1. Step 1: Identify correct parameter type for JSON array

   To accept a JSON array of User objects, the method parameter should be a List<User> annotated with @RequestBody.

2. Step 2: Exclude incorrect annotations and types

   @RequestParam and @PathVariable do not handle JSON body. Single User parameter cannot accept an array.

3. Final Answer:

   public int countUsers(@RequestBody List<User> users) -> Option B

4. Quick Check:

   JSON array maps to List<User> with @RequestBody [OK]

Hint: Use List<User> with @RequestBody for JSON arrays [OK]

Common Mistakes:

• Using single User instead of List<User>
• Using @RequestParam or @PathVariable for JSON body
• Forgetting @RequestBody annotation