@PostMapping for POST requests in Spring Boot - Performance & Optimization

Performance: @PostMapping for POST requests

MEDIUM IMPACT

This affects server response time and client perceived loading speed when handling POST requests.

Handling POST requests in a Spring Boot REST controller

Spring Boot

@PostMapping("/submit")
public CompletableFuture<ResponseEntity<String>> submitData(@RequestBody Data data) {
    return CompletableFuture.supplyAsync(() -> {
        processData(data); // async processing
        return ResponseEntity.ok("Success");
    });
}

Processes request asynchronously freeing server threads and reducing response delay.

📈 Performance Gainnon-blocking, faster response, improves LCP

Handling POST requests in a Spring Boot REST controller

Spring Boot

@PostMapping("/submit")
public ResponseEntity<String> submitData(@RequestBody Data data) {
    // heavy synchronous processing
    processData(data); // long blocking operation
    return ResponseEntity.ok("Success");
}

Blocking the request thread with heavy synchronous processing delays response and increases server load.

📉 Performance Costblocks server thread, increases response time, delays LCP

Performance Comparison

Pattern	Server Thread Usage	Response Delay	Client Impact	Verdict
Synchronous blocking in @PostMapping	High (blocks thread)	High (long delay)	Slow page load (LCP affected)	[X] Bad
Asynchronous processing in @PostMapping	Low (non-blocking)	Low (fast response)	Faster page load (better LCP)	[OK] Good

Rendering Pipeline

When a POST request is received, the server processes it before sending a response. Slow processing delays the browser's ability to render updated content.

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing (blocking operations in @PostMapping handler)

Core Web Vital Affected

LCP

This affects server response time and client perceived loading speed when handling POST requests.

Optimization Tips

1Avoid heavy synchronous processing inside @PostMapping handlers.

2Use asynchronous or background processing to keep server threads free.

3Monitor server response times to improve LCP and user experience.

Performance Quiz - 3 Questions

What is the main performance issue with synchronous processing inside a @PostMapping method?

A It causes client-side rendering delays directly.

B It reduces network bandwidth.

C It blocks the server thread, increasing response time.

D It increases CSS paint time.

DevTools: Network

How to check: Open DevTools, go to Network tab, submit the POST request, and observe the time taken for the request to complete.

What to look for: Look for long 'Waiting (TTFB)' times indicating server processing delays.

Practice

1. What is the main purpose of the @PostMapping annotation in Spring Boot?

easy

A. To map HTTP PUT requests to a specific method

B. To map HTTP POST requests to a specific method

C. To map HTTP DELETE requests to a specific method

D. To map HTTP GET requests to a specific method

Solution

1. Step 1: Understand HTTP methods

   HTTP POST is used to send data to the server, so a method handling POST requests must be mapped accordingly.

2. Step 2: Role of @PostMapping

   @PostMapping specifically maps HTTP POST requests to a method in a Spring Boot controller.

3. Final Answer:

   To map HTTP POST requests to a specific method -> Option B

4. Quick Check:

   @PostMapping = POST request handler [OK]

Hint: POST requests use @PostMapping to connect URL and method [OK]

Common Mistakes:

• Confusing @PostMapping with @GetMapping
• Using @PostMapping for GET requests
• Not understanding HTTP method differences

2. Which of the following is the correct syntax to create a POST endpoint in Spring Boot that accepts JSON data?

easy

A. @PostMapping("/submit")
public String submitData(String data) { return "Received"; }

B. @GetMapping("/submit")
public String submitData(@RequestBody String data) { return "Received"; }

C. @PostMapping("/submit")
public String submitData(@RequestBody String data) { return "Received"; }

D. @PostMapping("/submit")
public String submitData(@RequestParam String data) { return "Received"; }

Solution

1. Step 1: Identify correct annotation and parameter

   The method must use @PostMapping to handle POST requests and @RequestBody to receive JSON data from the request body.

2. Step 2: Check each option

   @PostMapping("/submit") public String submitData(@RequestBody String data) { return "Received"; } uses @PostMapping and @RequestBody correctly. @GetMapping("/submit") public String submitData(@RequestBody String data) { return "Received"; } uses @GetMapping which is wrong. @PostMapping("/submit") public String submitData(String data) { return "Received"; } misses @RequestBody, so data won't be parsed from JSON. @PostMapping("/submit") public String submitData(@RequestParam String data) { return "Received"; } uses @RequestParam which reads query parameters, not JSON body.

3. Final Answer:

   @PostMapping("/submit") public String submitData(@RequestBody String data) { return "Received"; } -> Option C

4. Quick Check:

   @PostMapping + @RequestBody = correct syntax [OK]

Hint: Use @RequestBody to get JSON data in POST method [OK]

Common Mistakes:

• Using @GetMapping instead of @PostMapping
• Forgetting @RequestBody for JSON input
• Using @RequestParam for JSON body data

3. Given the following Spring Boot controller method, what will be the output when a POST request with body "Hello" is sent to /greet? @PostMapping("/greet") public String greet(@RequestBody String name) { return "Hi, " + name + "!"; }

medium

A. "Hi, Hello!"

B. "Hello"

C. "Hi, name!"

D. HTTP 404 Not Found

Solution

1. Step 1: Understand method behavior

   The method takes the request body as a String parameter named 'name' and returns "Hi, " plus that name plus "!".

2. Step 2: Apply input to output

   Input body is "Hello", so the output will be "Hi, Hello!".

3. Final Answer:

   "Hi, Hello!" -> Option A

4. Quick Check:

   Input "Hello" returns "Hi, Hello!" [OK]

Hint: Return greeting by concatenating input string [OK]

Common Mistakes:

• Ignoring @RequestBody and expecting query param
• Confusing output with input
• Assuming endpoint is missing (404)

4. Identify the error in this Spring Boot POST method: @PostMapping("/addUser") public String addUser(String user) { return "User " + user + " added"; }

medium

A. Method return type should be void

B. Incorrect HTTP method annotation, should be @GetMapping

C. Missing @PathVariable annotation

D. Missing @RequestBody annotation for 'user' parameter

Solution

1. Step 1: Check parameter binding

   The method expects to receive data in the POST request body, so the parameter must be annotated with @RequestBody to bind JSON or raw data.

2. Step 2: Verify annotations

   Without @RequestBody, Spring won't map the request body to the 'user' parameter, causing it to be null or empty.

3. Final Answer:

   Missing @RequestBody annotation for 'user' parameter -> Option D

4. Quick Check:

   POST body needs @RequestBody on parameter [OK]

Hint: Add @RequestBody to method parameter for POST data [OK]

Common Mistakes:

• Forgetting @RequestBody on POST method parameters
• Using @GetMapping for POST endpoints
• Confusing @PathVariable with request body

5. You want to create a Spring Boot POST endpoint /register that accepts a JSON object with fields username and email, maps it to a Java record UserData(String username, String email), and returns a confirmation message. Which method signature correctly implements this?

hard

A. @PostMapping("/register")
public String registerUser(@RequestBody UserData user) {
return "User " + user.username() + " registered with email " + user.email();
}

B. @PostMapping("/register")
public String registerUser(UserData user) {
return "User " + user.username() + " registered";
}

C. @PostMapping("/register")
public String registerUser(@RequestParam UserData user) {
return "User " + user.username() + " registered";
}

D. @PostMapping("/register")
public String registerUser(@PathVariable UserData user) {
return "User " + user.username() + " registered";
}

Solution

1. Step 1: Understand data binding for POST JSON

   To map JSON request body to a Java record, the parameter must be annotated with @RequestBody.

2. Step 2: Check each option

   @PostMapping("/register") public String registerUser(@RequestBody UserData user) { return "User " + user.username() + " registered with email " + user.email(); } correctly uses @RequestBody with UserData record and accesses its fields. @PostMapping("/register") public String registerUser(UserData user) { return "User " + user.username() + " registered"; } misses @RequestBody, so mapping fails. Options C and D use @RequestParam and @PathVariable which are for query/path parameters, not JSON body.

3. Final Answer:

   @PostMapping("/register") public String registerUser(@RequestBody UserData user) { return "User " + user.username() + " registered with email " + user.email(); } -> Option A

4. Quick Check:

   @RequestBody + record parameter = correct POST JSON mapping [OK]

Hint: Use @RequestBody with record to map JSON POST data [OK]

Common Mistakes:

• Omitting @RequestBody on complex objects
• Using @RequestParam or @PathVariable for JSON body
• Not accessing record fields correctly