Why async processing matters in Spring Boot - Performance Evidence

Performance: Why async processing matters

HIGH IMPACT

Async processing improves server responsiveness and reduces request blocking, impacting user interaction speed and server throughput.

Handling long-running tasks in a web request

Spring Boot

public CompletableFuture<String> handleRequestAsync() {
  return CompletableFuture.supplyAsync(() -> {
    try {
      // Long operation
      Thread.sleep(5000);
    } catch (InterruptedException e) {
      throw new IllegalStateException(e);
    }
    return "done";
  });
}

Does not block server threads; frees them to handle other requests while processing continues asynchronously.

📈 Performance GainReduces blocking time per thread, improves INP and server scalability

Handling long-running tasks in a web request

Spring Boot

public String handleRequest() throws InterruptedException {
  // Long blocking operation
  Thread.sleep(5000);
  return "done";
}

Blocks the server thread for 5 seconds, preventing it from handling other requests.

📉 Performance CostBlocks rendering and response for 5 seconds, increasing INP and reducing throughput

Performance Comparison

Pattern	Thread Blocking	Request Throughput	Response Delay	Verdict
Synchronous blocking	Blocks thread for full task duration	Low under load	High delay	[X] Bad
Asynchronous processing	Releases thread immediately	High under load	Low delay	[OK] Good

Rendering Pipeline

Async processing frees server threads quickly, allowing faster response handling and reducing delays in sending data to the browser.

→Request Handling

→Response Generation

→Network Transfer

⚠️ BottleneckThread blocking during long operations delays response generation

Core Web Vital Affected

INP

Async processing improves server responsiveness and reduces request blocking, impacting user interaction speed and server throughput.

Optimization Tips

1Avoid blocking server threads during long operations.

2Use CompletableFuture or reactive programming for async tasks.

3Async processing improves server throughput and user input responsiveness.

Performance Quiz - 3 Questions

What is the main performance benefit of async processing in Spring Boot?

A It improves CSS rendering speed

B It reduces the size of the application bundle

C It prevents server threads from blocking during long tasks

D It decreases the number of HTTP requests

DevTools: Network and Performance panels

How to check: Record a performance profile during requests; check if server response times are long and if UI is blocked waiting for responses.

What to look for: Long server response times and delayed user interaction indicate blocking; shorter response times with smooth UI indicate good async usage.

Practice

1. Why is async processing important in Spring Boot applications?

easy

A. It makes the application use more memory by duplicating tasks.

B. It forces all tasks to run one after another in sequence.

C. It allows tasks to run in the background without blocking the main thread.

D. It disables error handling for faster execution.

Solution

1. Step 1: Understand async processing purpose

   Async processing lets tasks run separately from the main thread, so the app stays responsive.

2. Step 2: Identify correct behavior in Spring Boot

   Spring Boot uses @Async to run methods in the background, improving speed and user experience.

3. Final Answer:

   It allows tasks to run in the background without blocking the main thread. -> Option C

4. Quick Check:

   Async means background tasks = B [OK]

Hint: Async means background work without blocking main thread [OK]

Common Mistakes:

• Thinking async duplicates tasks unnecessarily
• Believing async forces sequential execution
• Assuming async disables error handling

2. Which annotation is used in Spring Boot to enable async processing on a method?

easy

A. @BackgroundTask

B. @EnableAsync

C. @AsyncMethod

D. @Async

Solution

1. Step 1: Recall Spring Boot async annotations

   @Async is the annotation placed on methods to run them asynchronously.

2. Step 2: Differentiate from other annotations

   @EnableAsync enables async support globally but is not placed on methods; @AsyncMethod and @BackgroundTask do not exist in Spring Boot.

3. Final Answer:

   @Async -> Option D

4. Quick Check:

   Method-level async annotation = A [OK]

Hint: Use @Async on methods to run them asynchronously [OK]

Common Mistakes:

• Confusing @EnableAsync with @Async
• Using non-existent annotations like @AsyncMethod
• Applying @Async on classes instead of methods

3. What will be the output behavior of this Spring Boot method annotated with @Async?

@Async
public CompletableFuture<String> fetchData() {
    // simulate delay
    Thread.sleep(1000);
    return CompletableFuture.completedFuture("Done");
}

medium

A. The method immediately returns a CompletableFuture, running the delay in the background.

B. The method returns null because async methods cannot return values.

C. The method throws a compile-time error due to Thread.sleep in async method.

D. The method blocks the caller for 1 second before returning "Done".

Solution

1. Step 1: Understand @Async with CompletableFuture

   @Async runs the method in a separate thread, so the caller gets a CompletableFuture immediately.

2. Step 2: Analyze Thread.sleep effect

   The delay happens inside the async thread, not blocking the caller thread.

3. Final Answer:

   The method immediately returns a CompletableFuture, running the delay in the background. -> Option A

4. Quick Check:

   @Async returns immediately with CompletableFuture = D [OK]

Hint: Async method returns CompletableFuture immediately, delay runs in background [OK]

Common Mistakes:

• Thinking Thread.sleep blocks the caller thread
• Assuming async methods cannot return values
• Believing async causes compile errors with sleep

4. Identify the error in this Spring Boot async method:

@Async
public void process() {
    CompletableFuture<String> result = CompletableFuture.supplyAsync(() -> {
        throw new RuntimeException("Fail");
    });
    System.out.println(result.get());
}

medium

A. Calling result.get() blocks the async thread, defeating async benefits.

B. Throwing RuntimeException inside supplyAsync is not allowed.

C. The method must return CompletableFuture<String>, not void.

D. Missing @EnableAsync annotation on the class.

Solution

1. Step 1: Analyze use of result.get()

   Calling get() waits for the CompletableFuture to finish, blocking the async thread.

2. Step 2: Understand async best practices

   Blocking defeats async purpose; exceptions inside supplyAsync are allowed and handled asynchronously.

3. Final Answer:

   Calling result.get() blocks the async thread, defeating async benefits. -> Option A

4. Quick Check:

   Blocking call inside async method = C [OK]

Hint: Avoid blocking calls like get() inside async methods [OK]

Common Mistakes:

• Thinking exceptions inside supplyAsync are disallowed
• Believing async methods must always return CompletableFuture
• Forgetting to enable async globally (not always required)

5. You want to improve a Spring Boot app's responsiveness by running multiple independent tasks in parallel. Which approach best uses async processing to achieve this?

hard

A. Run all tasks sequentially in the main thread to avoid thread overhead.

B. Annotate each task method with @Async and return CompletableFuture, then combine results with CompletableFuture.allOf().

C. Use @Async but return void from all methods to simplify code.

D. Create new threads manually inside each method without @Async.

Solution

1. Step 1: Identify best async pattern for parallel tasks

   Using @Async with CompletableFuture allows tasks to run in parallel and return results.

2. Step 2: Combine results properly

   CompletableFuture.allOf() waits for all async tasks to finish, enabling coordinated processing.

3. Final Answer:

   Annotate each task method with @Async and return CompletableFuture, then combine results with CompletableFuture.allOf(). -> Option B

4. Quick Check:

   Parallel async tasks + combine results = A [OK]

Hint: Use @Async + CompletableFuture.allOf() for parallel task coordination [OK]

Common Mistakes:

• Running tasks sequentially loses async benefits
• Returning void loses ability to track task completion
• Manually creating threads ignores Spring Boot async support