Using CompletableFuture with Streams for Parallel Execution in Java

Introduction: To improve API response speed, business logic can be parallelized using Java's JUC concurrency tools, especially CompletableFuture.

CompletableFuture provides methods such as public static <U> CompletableFuture<U> supplyAsync(Supplier<U> supplier, Executor executor) { return asyncSupplyStage(screenExecutor(executor), supplier); } , allowing easy asynchronous execution with a custom thread pool and offering powerful task composition and exception handling.

Developers often combine CompletableFuture with Java streams to achieve asynchronous parallel execution, but an incorrect usage pattern can result in no real parallelism. A common mistake is processing the stream as list → stream → map(CompletableFuture) → map(CompletableFuture::join) → toList , which executes tasks sequentially.

Correct approach: split the processing into two streams—first create a stream of CompletableFuture objects, then apply a terminal operation (e.g., toList() ) to trigger evaluation. Because intermediate stream operations are lazy, only the terminal operation forces the asynchronous tasks to start.

By converting each element to a CompletableFuture and using a terminal operation like toList() , the asynchronous tasks begin execution immediately, achieving true parallelism.

Conclusion: When using CompletableFuture with streams, always separate the creation of CompletableFuture streams and apply a terminal operation to ensure asynchronous execution starts as intended.