@Async for async methods in Spring Boot - Performance & Optimization

Performance: @Async for async methods

MEDIUM IMPACT

This affects how quickly the server responds to requests by running methods asynchronously, improving user interaction speed.

Running a long task without blocking the main request thread

Spring Boot

@Async
public void longTask() throws InterruptedException {
  Thread.sleep(5000); // simulate long work
}

@GetMapping("/process")
public String process() {
  longTask(); // runs asynchronously
  return "done";
}

The long task runs in a separate thread, so the request returns immediately without waiting.

📈 Performance GainNon-blocking request thread, improves INP by reducing response delay.

Running a long task without blocking the main request thread

Spring Boot

@GetMapping("/process")
public String process() throws InterruptedException {
  longTask(); // runs synchronously
  return "done";
}

public void longTask() throws InterruptedException {
  Thread.sleep(5000); // simulate long work
}

The request thread waits for the long task to finish, blocking response and causing slow user experience.

📉 Performance CostBlocks main thread for 5 seconds, increasing INP and delaying response.

Performance Comparison

Pattern	Thread Blocking	Response Delay	Server Load	Verdict
Synchronous method call	Blocks main thread	High delay	Lower concurrency	[X] Bad
@Async method call	No main thread block	Low delay	Higher concurrency	[OK] Good

Rendering Pipeline

The @Async annotation causes the method to run in a separate thread pool, freeing the main request thread to respond faster. This reduces server-side blocking and improves how quickly the browser receives a response.

→Server Request Handling

→Thread Management

⚠️ BottleneckMain request thread blocking during long synchronous tasks

Core Web Vital Affected

INP

This affects how quickly the server responds to requests by running methods asynchronously, improving user interaction speed.

Optimization Tips

1Use @Async to run long tasks in background threads to avoid blocking requests.

2Configure thread pools to prevent thread exhaustion when using @Async.

3Monitor server response times to ensure asynchronous methods improve performance.

Performance Quiz - 3 Questions

What is the main performance benefit of using @Async on a method in Spring Boot?

A It compresses the response to reduce network load.

B It runs the method in a separate thread, reducing request blocking.

C It caches the method result to speed up future calls.

D It delays method execution until the server is idle.

DevTools: Network

How to check: Open DevTools, go to Network tab, trigger the request, and observe the response time.

What to look for: Faster Time To First Byte (TTFB) indicates the server responded quickly without blocking.

Practice

1.

What is the main purpose of using @Async in a Spring Boot application?

easy

A. To secure methods with authentication

B. To make methods run faster by optimizing CPU usage

C. To automatically retry failed methods

D. To run methods in the background without blocking the main thread

Solution

1. Step 1: Understand what @Async does

   @Async allows methods to run in a separate thread, so they don't block the main thread.

2. Step 2: Identify the main benefit

   This helps keep the app responsive by running long tasks in the background.

3. Final Answer:

   To run methods in the background without blocking the main thread -> Option D

4. Quick Check:

   Background execution = To run methods in the background without blocking the main thread [OK]

Hint: Async means background task, not faster or secure [OK]

Common Mistakes:

• Thinking @Async speeds up method execution
• Confusing @Async with security annotations
• Assuming @Async retries failed methods automatically

2.

Which annotation must be added to a Spring Boot configuration class to enable @Async support?

easy

A. @EnableAsync

B. @EnableScheduling

C. @AsyncSupport

D. @EnableAsyncSupport

Solution

1. Step 1: Recall the enabling annotation for async

   Spring Boot requires @EnableAsync on a configuration class to activate async processing.

2. Step 2: Confirm the exact annotation name

   The correct annotation is @EnableAsync, not any other variant.

3. Final Answer:

   @EnableAsync -> Option A

4. Quick Check:

   Enable async = @EnableAsync [OK]

Hint: Enable async with @EnableAsync, not similar names [OK]

Common Mistakes:

• Using @EnableScheduling instead of @EnableAsync
• Guessing annotation names without checking docs
• Confusing @Async with enabling annotations

3.

Consider this Spring Boot method annotated with @Async:

  @Async
  public CompletableFuture<String> fetchData() {
    return CompletableFuture.completedFuture("Done");
  }

What will be the output if you call fetchData().get()?

medium

A. It blocks until the async task completes and returns "Done"

B. It throws a NullPointerException

C. It returns "Done" immediately

D. It returns null because async methods don't return values

Solution

1. Step 1: Understand CompletableFuture with @Async

   The method returns a CompletableFuture that completes immediately with "Done".

2. Step 2: Calling get() on CompletableFuture

   Calling get() blocks the caller until the async task finishes and then returns the result.

3. Final Answer:

   It blocks until the async task completes and returns "Done" -> Option A

4. Quick Check:

   CompletableFuture.get() blocks and returns result [OK]

Hint: CompletableFuture.get() waits for async result [OK]

Common Mistakes:

• Assuming async methods return immediately without blocking on get()
• Thinking async methods can't return values
• Confusing exceptions with null returns

4.

Given this Spring Boot service method:

  @Async
  public void process() {
    System.out.println("Start");
    throw new RuntimeException("Error");
  }

What happens when process() is called?

medium

A. The exception is thrown on the caller thread immediately

B. The exception is logged but does not affect the caller thread

C. The method runs synchronously and throws the exception normally

D. The exception is ignored silently

Solution

1. Step 1: Understand exception handling in @Async methods

   Exceptions in async methods run in a separate thread and do not propagate to the caller.

2. Step 2: What happens to the exception?

   The exception is logged by Spring but does not crash or throw on the caller thread.

3. Final Answer:

   The exception is logged but does not affect the caller thread -> Option B

4. Quick Check:

   Async exceptions logged, caller unaffected [OK]

Hint: Async exceptions don't throw on caller thread [OK]

Common Mistakes:

• Expecting exceptions to propagate to caller immediately
• Thinking async methods run synchronously
• Assuming exceptions are ignored silently

5.

You want to run two independent tasks asynchronously and wait concurrently for both to finish before proceeding. Which approach using @Async and CompletableFuture is correct?

  @Async
  public CompletableFuture<String> taskOne() { ... }

  @Async
  public CompletableFuture<String> taskTwo() { ... }

  public void runTasks() throws Exception {
    CompletableFuture<String> future1 = taskOne();
    CompletableFuture<String> future2 = taskTwo();
    // What to do here?
  }

hard

A. Just call taskOne() and taskTwo() without waiting

B. Call future1.get() and future2.get() sequentially to wait

C. Use CompletableFuture.allOf(future1, future2).join() to wait both

D. Call future1.complete() and future2.complete() manually

Solution

1. Step 1: Understand waiting for multiple async tasks

   Calling get() sequentially works but is inefficient and blocks one after another.

2. Step 2: Use CompletableFuture.allOf for parallel waiting

   CompletableFuture.allOf(future1, future2).join() waits for both tasks to complete concurrently.

3. Final Answer:

   Use CompletableFuture.allOf(future1, future2).join() to wait both -> Option C

4. Quick Check:

   Wait all async tasks with allOf().join() [OK]

Hint: Use allOf().join() to wait multiple async tasks together [OK]

Common Mistakes:

• Calling get() sequentially causing unnecessary blocking
• Not waiting at all and proceeding too early
• Trying to manually complete futures which is incorrect