Course contentsShow
← Java
Lesson 2739 of 2,87050. Executor FrameworkFree lesson

What is a Future? Asynchronous Computation Results

Learn how Future represents the result of an asynchronous computation that may not be available yet.

What is a Future? Asynchronous Computation Results

You'll learn: What a Future represents and how it lets you retrieve results from tasks that may still be running.

The Core Idea

A Future<V> is Java's way of giving you a "receipt" for work you've submitted to an executor. When you use submit() instead of execute(), you get back a Future object immediately—even though the task hasn't finished (or maybe hasn't even started) yet. This Future acts as a handle to the eventual result.

Think of it like ordering food at a busy restaurant. The waiter gives you a number ticket immediately, but your meal isn't ready yet. That ticket is your "future"—you can check if the food is ready, wait for it, or even cancel your order before it's prepared.

Why Futures Matter

When you submit a task to an executor, the calling thread doesn't wait around—it continues executing. But what if you need the result later? The Future bridges this gap. It represents:

  • A promise of a result: The computation will eventually produce a value of type V
  • Current task state: Is it still running? Finished? Cancelled?
  • A retrieval mechanism: You can block until the result is available

The Async Workflow

  1. Submit a Callable<V> to an ExecutorService
  2. Get a Future<V> back immediately (no waiting)
  3. Do other work in the meantime
  4. When you need the result, call methods on the Future (more on these methods in upcoming lessons)

Key Takeaway: A Future is a handle to the result of an asynchronous computation, letting you retrieve outcomes from tasks submitted to executors without blocking immediately—you control when to wait for completion.