Why async processing matters in Spring Boot - Challenge Your Understanding

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when a Spring Boot controller method is annotated with @Async?

Consider a Spring Boot REST controller method annotated with @Async. What is the behavior when this method is called?

Spring Boot

import org.springframework.scheduling.annotation.Async;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;
import java.util.concurrent.CompletableFuture;

@RestController
public class AsyncController {

    @Async
    @GetMapping("/async")
    public CompletableFuture<String> asyncMethod() {
        return CompletableFuture.supplyAsync(() -> {
            try {
                Thread.sleep(1000);
            } catch (InterruptedException e) {
                Thread.currentThread().interrupt();
            }
            return "Done";
        });
    }
}

A The method throws an exception because @Async cannot be used on controller methods.

B The method blocks the caller thread until the task completes and then returns the result.

C The method runs in a separate thread and immediately returns a CompletableFuture to the caller.

D The method runs synchronously but logs the execution asynchronously.

💡 Hint

Think about how @Async changes the thread behavior of the method.

When a method is annotated with @Async in Spring Boot, it runs in a separate thread managed by Spring's task executor. The method returns immediately with a CompletableFuture, allowing the caller to continue without waiting for the method to finish.

❓ state_output

intermediate

What is the output when calling an async method without waiting for the result?

Given a Spring Boot service method annotated with @Async that returns a CompletableFuture, what will be printed if the caller does not wait for the CompletableFuture to complete?

Spring Boot

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

@Service
public class AsyncService {

    @Async
    public CompletableFuture<String> fetchData() {
        try {
            Thread.sleep(500);
        } catch (InterruptedException e) {
            Thread.currentThread().interrupt();
        }
        return CompletableFuture.completedFuture("Data Ready");
    }
}

// Caller code (Spring-managed bean):
CompletableFuture<String> future = service.fetchData();
System.out.println("Result: " + future.getNow("Not Ready"));

A Result: Not Ready

B Result: Data Ready

C Compilation error because getNow cannot be used here

D Runtime exception due to calling getNow on incomplete future

💡 Hint

Check what getNow returns if the CompletableFuture is not done yet.

The getNow method returns the given default value if the CompletableFuture is not completed yet. Since the async method sleeps for 500ms and the print happens immediately, the future is not done, so it prints the default value.

📝 Syntax

advanced

Which code snippet correctly enables async processing in Spring Boot?

To use @Async in a Spring Boot application, which of the following code snippets correctly enables async support?

A

@EnableTransactionManagement
@SpringBootApplication
public class App {}

B

@EnableAsync
@SpringBootApplication
public class App {}

C

@EnableScheduling
@SpringBootApplication
public class App {}

D

@Async
@SpringBootApplication
public class App {}

💡 Hint

Look for the annotation that activates async processing in Spring.

The @EnableAsync annotation enables Spring's asynchronous method execution capability. Without it, @Async annotations have no effect.

🔧 Debug

advanced

Why does this async method not run asynchronously?

Given the following Spring Boot service, why does the async method run synchronously instead of asynchronously?

Spring Boot

import org.springframework.scheduling.annotation.Async;
import org.springframework.stereotype.Service;

@Service
public class MyService {

    @Async
    public void asyncTask() {
        System.out.println("Running async task");
    }

    public void callAsync() {
        asyncTask();
    }
}

A Because asyncTask() is called from within the same class, Spring's proxy does not intercept the call to run it asynchronously.

B Because the @Async annotation is missing the executor parameter.

C Because the method asyncTask() must return a Future or CompletableFuture to be async.

D Because the @Service annotation disables async processing.

💡 Hint

Think about how Spring proxies work for async methods.

Spring uses proxies to intercept calls to @Async methods. When a method is called from within the same class, the proxy is bypassed, so the method runs synchronously.

🧠 Conceptual

expert

Why is async processing important in web applications?

Which of the following best explains why asynchronous processing matters in web applications built with Spring Boot?

A It automatically caches all responses to speed up future requests.

B It guarantees that all tasks run in parallel, eliminating any waiting time completely.

C It simplifies code by removing the need for error handling in background tasks.

D It allows the server to handle more requests by freeing up threads while waiting for long tasks, improving scalability and user experience.

💡 Hint

Think about how threads and waiting affect server performance.

Async processing frees up server threads during long-running tasks, allowing the server to handle more requests simultaneously. This improves scalability and responsiveness.