@Async for async methods in Spring Boot

Introduction

@Async lets your program do tasks in the background without waiting. This helps your app stay fast and responsive.

When you want to send emails without making the user wait.

When you need to process files or data without blocking the main work.

When calling slow external services but want to keep your app quick.

When running scheduled tasks that should not stop other actions.

Syntax

Spring Boot

@Async
public CompletableFuture<Type> methodName() {
    // method body
}

Use @Async above a method to run it in a new thread.

The method should return CompletableFuture or void.

Examples

This method runs in the background and returns nothing.

Spring Boot

@Async
public void sendEmail() {
    // send email code
}

This method runs async and returns a future result.

Spring Boot

@Async
public CompletableFuture<String> fetchData() {
    // fetch data code
    return CompletableFuture.completedFuture("data");
}

Sample Program

This example shows a service with an async method that waits 1 second then returns a message. The main runner calls it without blocking, then waits for the result to print.

Spring Boot

import org.springframework.scheduling.annotation.Async;
import org.springframework.scheduling.annotation.EnableAsync;
import org.springframework.stereotype.Service;
import org.springframework.context.annotation.Configuration;
import java.util.concurrent.CompletableFuture;

@Configuration
@EnableAsync
public class AsyncConfig {
}

@Service
public class AsyncService {

    @Async
    public CompletableFuture<String> asyncTask() {
        try {
            Thread.sleep(1000); // simulate delay
        } catch (InterruptedException e) {
            Thread.currentThread().interrupt();
        }
        return CompletableFuture.completedFuture("Task Completed");
    }
}

// Usage in another component
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.CommandLineRunner;
import org.springframework.stereotype.Component;
import java.util.concurrent.CompletableFuture;

@Component
public class AppRunner implements CommandLineRunner {

    @Autowired
    private AsyncService asyncService;

    @Override
    public void run(String... args) throws Exception {
        System.out.println("Starting async call");
        CompletableFuture<String> future = asyncService.asyncTask();
        System.out.println("Async call made");
        System.out.println("Result: " + future.get());
    }
}

Important Notes

Remember to add @EnableAsync in your configuration to activate async support.

Async methods must be public and called from outside their own class to work properly.

Summary

@Async runs methods in the background to keep your app responsive.

Use it for tasks that take time but don't need to block the user.

Make sure to enable async support with @EnableAsync.

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