Course contentsShow
← Java
Lesson 2783 of 2,87051. CompletableFutureFree lesson

The get and join Methods: Blocking for Results

Using get() and join() to block and retrieve results, and understanding when blocking is appropriate.

The get and join Methods: Blocking for Results

You'll learn how to extract results from a CompletableFuture using blocking methods and when this approach makes sense.

Understanding Blocking Retrieval

While CompletableFuture excels at non-blocking asynchronous programming, sometimes you genuinely need to wait for a result. Both get() and join() block the calling thread until the CompletableFuture completes, then return the result.

The get Method

get() forces you to handle checked exceptions:

CompletableFuture<String> future = CompletableFuture.completedFuture("Ready");

try {
    String result = future.get(); // blocks until complete
    System.out.println(result);
} catch (InterruptedException | ExecutionException e) {
    // handle errors
}

You can also use get(timeout) to avoid indefinite blocking, just like with regular Futures.

The join Method

join() is similar but throws unchecked exceptions, making it cleaner in lambda expressions and streams:

CompletableFuture<String> future = CompletableFuture.completedFuture("Ready");

String result = future.join(); // no try-catch required

If the task failed, join() wraps the cause in a CompletionException (unchecked).

When Blocking is Appropriate

Use these methods when:

  • You're at a natural synchronization point (like the end of main())
  • You need results before proceeding with non-parallelizable logic
  • Testing or debugging asynchronous code

Avoid using them inside CompletableFuture chains—that defeats the non-blocking design.

Key Takeaway: Use get() when you need timeout control or are handling checked exceptions explicitly; use join() for cleaner code in functional pipelines. Both block the thread, so reserve them for true synchronization points.