Use CompletableFuture

The fastest way to misunderstand CompletableFuture is to memorize its surface syntax without learning the boundary it controls. We will use build a small domain application that grows into tested Spring-backed services as a concrete thread, so each choice has an observable consequence rather than becoming a list of disconnected facts.

In this lesson

• Place CompletableFuture in the context of the Concurrency and I/O module rather than treating it as an isolated feature.
• Build a mental model for what happens before, during, and after the operation.
• Work through a reproducible example connected to the scenario: build a small domain application that grows into tested Spring-backed services.
• Inspect the result and distinguish evidence from assumption.
• Recognize failure modes, misleading shortcuts, and production constraints.
• Leave with a verification checklist and a practical exercise rather than a memorized snippet.

Build a baseline

For a Java developer, CompletableFuture becomes useful when it changes a decision you can verify. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—build a small domain application that grows into tested Spring-backed services—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by CompletableFuture; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. For CompletableFuture, apply this check in the context of the Concurrency and I/O workflow before carrying the assumption into later Java work.

The practical question behind use completablefuture is not simply whether the feature exists, but what behavior it gives you control over. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. In this lesson's CompletableFuture example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Concurrency and I/O exercise changes the conditions. In Java lesson 37 — Use CompletableFuture, use that observation as the checkpoint for this exact Concurrency and I/O topic rather than generalizing it beyond the evidence.

Understand the execution path

Before adding more syntax, make the state of the system observable. That habit matters especially when working with CompletableFuture. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—build a small domain application that grows into tested Spring-backed services—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by CompletableFuture; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. Keep this point tied to CompletableFuture. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Concurrency and I/O lesson are specific to this mechanism.

There are usually several ways to accomplish the same visible result. The important skill is knowing which guarantees differ when you choose one form of CompletableFuture over another. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. In this lesson's CompletableFuture example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Concurrency and I/O exercise changes the conditions. In Java lesson 37 — Use CompletableFuture, use that observation as the checkpoint for this exact Concurrency and I/O topic rather than generalizing it beyond the evidence.

Questions to answer about CompletableFuture

1. What is the smallest input or state that makes CompletableFuture observable?
2. What does success look like, and how can you prove it without relying on a vague UI message?
3. Which configuration, permissions, types, versions or environment details can change the result?
4. Which failure is most likely for a beginner, and what evidence distinguishes it from a different failure?
5. What should remain true after the example is repeated, automated or moved to another environment?

Find the dominant cost

In the Concurrency and I/O part of this learning path, CompletableFuture is deliberately introduced now because later lessons depend on the boundary it establishes. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—build a small domain application that grows into tested Spring-backed services—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by CompletableFuture; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. In this lesson's CompletableFuture example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Concurrency and I/O exercise changes the conditions. In Java lesson 37 — Use CompletableFuture, use that observation as the checkpoint for this exact Concurrency and I/O topic rather than generalizing it beyond the evidence.

A production system rarely fails at the exact line shown in a beginner example, so this section connects CompletableFuture to the surrounding runtime and operational context. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. The specific test here is about CompletableFuture: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

Optimization levers and their trade-offs

For a Java developer, CompletableFuture becomes useful when it changes a decision you can verify. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—build a small domain application that grows into tested Spring-backed services—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by CompletableFuture; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. Keep this point tied to CompletableFuture. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Concurrency and I/O lesson are specific to this mechanism.

The practical question behind use completablefuture is not simply whether the feature exists, but what behavior it gives you control over. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. For CompletableFuture, apply this check in the context of the Concurrency and I/O workflow before carrying the assumption into later Java work. In Java lesson 37 — Use CompletableFuture, use that observation as the checkpoint for this exact Concurrency and I/O topic rather than generalizing it beyond the evidence.

Evidence table

What you inspect	What it tells you	What it does not prove
Source/configuration for CompletableFuture	What you asked the platform/runtime to do	That the request actually succeeded
Build/validation output	Whether static checks accepted the artifact	That production data and permissions behave correctly
Runtime/result output	What happened for this input	That every edge case is safe
Logs/diagnostics	Where the system spent time or failed	The root cause without interpretation
Repeat test	Whether behavior is reproducible	That the design is optimal

A measurable worked example

Before adding more syntax, make the state of the system observable. That habit matters especially when working with CompletableFuture. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—build a small domain application that grows into tested Spring-backed services—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by CompletableFuture; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. For CompletableFuture, apply this check in the context of the Concurrency and I/O workflow before carrying the assumption into later Java work. In Java lesson 37 — Use CompletableFuture, use that observation as the checkpoint for this exact Concurrency and I/O topic rather than generalizing it beyond the evidence.

There are usually several ways to accomplish the same visible result. The important skill is knowing which guarantees differ when you choose one form of CompletableFuture over another. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. For CompletableFuture, apply this check in the context of the Concurrency and I/O workflow before carrying the assumption into later Java work.

Read the plan/profile/metrics

In the Concurrency and I/O part of this learning path, CompletableFuture is deliberately introduced now because later lessons depend on the boundary it establishes. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—build a small domain application that grows into tested Spring-backed services—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by CompletableFuture; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. For CompletableFuture, apply this check in the context of the Concurrency and I/O workflow before carrying the assumption into later Java work.

A production system rarely fails at the exact line shown in a beginner example, so this section connects CompletableFuture to the surrounding runtime and operational context. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. Keep this point tied to CompletableFuture. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Concurrency and I/O lesson are specific to this mechanism.

Worked example: CompletableFuture

The following java example is written specifically for this lesson. Read the requirement first, then predict the important result before running or reproducing it.

import java.util.ArrayList;
import java.util.List;

public class Main {
    public static void main(String[] args) {
        List<Integer> values = new ArrayList<>(List.of(12, 18, 25, 31));
        values.removeIf(value -> value < 20);
        System.out.println(values);
    }
}
``` Keep this point tied to **CompletableFuture**. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Concurrency and I/O lesson are specific to this mechanism.

**Expected observation**

[25, 31]

### Read the example deliberately

- **Line/construct 1:** `import java.util.ArrayList;` — identify what state or contract this introduces, then trace where that state is consumed.
- **Line/construct 2:** `import java.util.List;` — identify what state or contract this introduces, then trace where that state is consumed.
- **Line/construct 3:** `public class Main {` — identify what state or contract this introduces, then trace where that state is consumed.
- **Line/construct 4:** `public static void main(String[] args) {` — identify what state or contract this introduces, then trace where that state is consumed.
- **Line/construct 5:** `List<Integer> values = new ArrayList<>(List.of(12, 18, 25, 31));` — identify what state or contract this introduces, then trace where that state is consumed.
- **Line/construct 6:** `values.removeIf(value -> value < 20);` — identify what state or contract this introduces, then trace where that state is consumed.
- **Line/construct 7:** `System.out.println(values);` — identify what state or contract this introduces, then trace where that state is consumed.
- **Line/construct 8:** `}` — identify what state or contract this introduces, then trace where that state is consumed.
- **Line/construct 9:** `}` — identify what state or contract this introduces, then trace where that state is consumed.

Do not stop at “it ran.” Change one meaningful value related to CompletableFuture, predict the new result, run/reproduce the example again, and explain why the output changed. That mutation test is a stronger check of understanding than copying the original result.

## Concurrency and contention concerns

For a Java developer, CompletableFuture becomes useful when it changes a decision you can verify. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—build a small domain application that grows into tested Spring-backed services—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by CompletableFuture; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. In this lesson's **CompletableFuture** example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Concurrency and I/O exercise changes the conditions. In **Java lesson 37 — Use CompletableFuture**, use that observation as the checkpoint for this exact Concurrency and I/O topic rather than generalizing it beyond the evidence.

For this part of **Use CompletableFuture**, move beyond the earlier mental model and ask how the behavior survives repetition. Run or reproduce the step twice, change the ordering or boundary case where safe, and verify that the same invariant still holds. A reliable Concurrency and I/O workflow is one that produces evidence you can compare, not one that succeeds only when the exact tutorial sequence is copied.

## Memory and allocation considerations

Now apply **CompletableFuture** to the current **Memory and allocation considerations** concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Java runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

This section needs a different question from the earlier explanation: what would make **CompletableFuture** fail specifically while working through **Memory and allocation considerations**? Choose one realistic boundary, reproduce it deliberately, and inspect the first useful diagnostic or intermediate value. The aim in Use CompletableFuture is to recognize the mechanism under changed conditions, not to repeat the same successful path with different wording.

### Failure-mode matrix

| Symptom | Likely category | First evidence to collect |
|---|---|---|
| The CompletableFuture behavior never occurs | configuration / control flow | verify the relevant code/configuration is actually reached |
| Build or validation fails | syntax / type / unsupported option | read the first meaningful diagnostic, not the last cascade message |
| Works locally but not elsewhere | environment / version / permission | compare runtime versions, identity, configuration and data |
| Result is valid but wrong | assumption / data shape / business rule | inspect intermediate values and boundary conditions |
| Intermittent behavior | concurrency / timing / external dependency | add timestamps, correlation IDs or deterministic reproduction |

## Caching: useful or dangerous?

For the **Caching: useful or dangerous?** part of Use CompletableFuture, use a separate verification pass rather than repeating the earlier explanation. Focus on **CompletableFuture** under one changed condition and write down the before/after evidence. This is verification pass 2 for Java lesson 37: the useful outcome is a concrete observation—output, state, diagnostic, generated artifact, query result or test result—that another learner can reproduce in the Concurrency and I/O workflow.

A production system rarely fails at the exact line shown in a beginner example, so this section connects CompletableFuture to the surrounding runtime and operational context. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. For **CompletableFuture**, apply this check in the context of the **Concurrency and I/O** workflow before carrying the assumption into later Java work. In **Java lesson 37 — Use CompletableFuture**, use that observation as the checkpoint for this exact Concurrency and I/O topic rather than generalizing it beyond the evidence.

## Regression testing

For a Java developer, CompletableFuture becomes useful when it changes a decision you can verify. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—build a small domain application that grows into tested Spring-backed services—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by CompletableFuture; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. The specific test here is about **CompletableFuture**: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

The practical question behind use completablefuture is not simply whether the feature exists, but what behavior it gives you control over. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. The specific test here is about **CompletableFuture**: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

## Production observability

For the **Production observability** part of Use CompletableFuture, use a separate verification pass rather than repeating the earlier explanation. Focus on **CompletableFuture** under one changed condition and write down the before/after evidence. This is verification pass 3 for Java lesson 37: the useful outcome is a concrete observation—output, state, diagnostic, generated artifact, query result or test result—that another learner can reproduce in the Concurrency and I/O workflow.

There are usually several ways to accomplish the same visible result. The important skill is knowing which guarantees differ when you choose one form of CompletableFuture over another. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. The specific test here is about **CompletableFuture**: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

## Performance checklist

In the Concurrency and I/O part of this learning path, CompletableFuture is deliberately introduced now because later lessons depend on the boundary it establishes. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—build a small domain application that grows into tested Spring-backed services—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by CompletableFuture; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. The specific test here is about **CompletableFuture**: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

For the **Performance checklist** part of Use CompletableFuture, use a separate verification pass rather than repeating the earlier explanation. Focus on **CompletableFuture** under one changed condition and write down the before/after evidence. This is verification pass 4 for Java lesson 37: the useful outcome is a concrete observation—output, state, diagnostic, generated artifact, query result or test result—that another learner can reproduce in the Concurrency and I/O workflow.

## Measure before optimizing CompletableFuture

For the **Measure before optimizing CompletableFuture** part of Use CompletableFuture, use a separate verification pass rather than repeating the earlier explanation. Focus on **CompletableFuture** under one changed condition and write down the before/after evidence. This is verification pass 5 for Java lesson 37: the useful outcome is a concrete observation—output, state, diagnostic, generated artifact, query result or test result—that another learner can reproduce in the Concurrency and I/O workflow.

In **Measure before optimizing CompletableFuture**, look at **CompletableFuture** through the constraint that matters in this part of the lesson: make the relevant state visible before you change it, then compare the observed result with the contract you expected. In Java, this prevents a local-looking edit from hiding an environment, data, permission, lifecycle or runtime assumption. Record the evidence from this step because the next decision in the Concurrency and I/O module should be based on what you measured rather than on a repeated rule of thumb.

## Where time and resources are actually spent

Before adding more syntax, make the state of the system observable. That habit matters especially when working with CompletableFuture. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—build a small domain application that grows into tested Spring-backed services—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by CompletableFuture; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. The specific test here is about **CompletableFuture**: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

This section needs a different question from the earlier explanation: what would make **CompletableFuture** fail specifically while working through **Where time and resources are actually spent**? Choose one realistic boundary, reproduce it deliberately, and inspect the first useful diagnostic or intermediate value. The aim in Use CompletableFuture is to recognize the mechanism under changed conditions, not to repeat the same successful path with different wording.

## A production-oriented walkthrough for CompletableFuture

### 1. Establish the CompletableFuture behavior

Establish this step in the context of build a small domain application that grows into tested Spring-backed services. Keep the change small enough that you can state the expected result before executing it. Capture the relevant input, configuration or code, then record the observable result. If the result differs from the prediction, do not add more changes yet; narrow the mismatch using diagnostics appropriate to a modern JDK, IntelliJ/VS Code and build tooling. Keep this point tied to **CompletableFuture**. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Concurrency and I/O lesson are specific to this mechanism.

### 2. Inspect the CompletableFuture behavior

Inspect this step in the context of build a small domain application that grows into tested Spring-backed services. Keep the change small enough that you can state the expected result before executing it. Capture the relevant input, configuration or code, then record the observable result. If the result differs from the prediction, do not add more changes yet; narrow the mismatch using diagnostics appropriate to a modern JDK, IntelliJ/VS Code and build tooling. The specific test here is about **CompletableFuture**: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

### 3. Implement the CompletableFuture behavior

Implement this step in the context of build a small domain application that grows into tested Spring-backed services. Keep the change small enough that you can state the expected result before executing it. Capture the relevant input, configuration or code, then record the observable result. If the result differs from the prediction, do not add more changes yet; narrow the mismatch using diagnostics appropriate to a modern JDK, IntelliJ/VS Code and build tooling. For **CompletableFuture**, apply this check in the context of the **Concurrency and I/O** workflow before carrying the assumption into later Java work.

A useful variation is to introduce one boundary case that is plausible for CompletableFuture: an empty value, a missing permission, an unexpected type, a repeated operation, an unavailable dependency, or a larger-than-normal input. The exact case depends on the technology, but the reasoning is the same—state the invariant you expect to remain true, then verify it explicitly. The specific test here is about **CompletableFuture**: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

### 4. Exercise the CompletableFuture behavior

Exercise this step in the context of build a small domain application that grows into tested Spring-backed services. Keep the change small enough that you can state the expected result before executing it. Capture the relevant input, configuration or code, then record the observable result. If the result differs from the prediction, do not add more changes yet; narrow the mismatch using diagnostics appropriate to a modern JDK, IntelliJ/VS Code and build tooling. The specific test here is about **CompletableFuture**: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

### 5. Challenge the CompletableFuture behavior

Challenge this step in the context of build a small domain application that grows into tested Spring-backed services. Keep the change small enough that you can state the expected result before executing it. Capture the relevant input, configuration or code, then record the observable result. If the result differs from the prediction, do not add more changes yet; narrow the mismatch using diagnostics appropriate to a modern JDK, IntelliJ/VS Code and build tooling. In this lesson's **CompletableFuture** example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Concurrency and I/O exercise changes the conditions.

A useful variation is to introduce one boundary case that is plausible for CompletableFuture: an empty value, a missing permission, an unexpected type, a repeated operation, an unavailable dependency, or a larger-than-normal input. The exact case depends on the technology, but the reasoning is the same—state the invariant you expect to remain true, then verify it explicitly. For **CompletableFuture**, apply this check in the context of the **Concurrency and I/O** workflow before carrying the assumption into later Java work.

### 6. Verify the CompletableFuture behavior

Verify this step in the context of build a small domain application that grows into tested Spring-backed services. Keep the change small enough that you can state the expected result before executing it. Capture the relevant input, configuration or code, then record the observable result. If the result differs from the prediction, do not add more changes yet; narrow the mismatch using diagnostics appropriate to a modern JDK, IntelliJ/VS Code and build tooling. Keep this point tied to **CompletableFuture**. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Concurrency and I/O lesson are specific to this mechanism.

### 7. Harden the CompletableFuture behavior

Harden this step in the context of build a small domain application that grows into tested Spring-backed services. Keep the change small enough that you can state the expected result before executing it. Capture the relevant input, configuration or code, then record the observable result. If the result differs from the prediction, do not add more changes yet; narrow the mismatch using diagnostics appropriate to a modern JDK, IntelliJ/VS Code and build tooling. Keep this point tied to **CompletableFuture**. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Concurrency and I/O lesson are specific to this mechanism.

A useful variation is to introduce one boundary case that is plausible for CompletableFuture: an empty value, a missing permission, an unexpected type, a repeated operation, an unavailable dependency, or a larger-than-normal input. The exact case depends on the technology, but the reasoning is the same—state the invariant you expect to remain true, then verify it explicitly. In this lesson's **CompletableFuture** example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Concurrency and I/O exercise changes the conditions.

### 8. Document the CompletableFuture behavior

Document this step in the context of build a small domain application that grows into tested Spring-backed services. Keep the change small enough that you can state the expected result before executing it. Capture the relevant input, configuration or code, then record the observable result. If the result differs from the prediction, do not add more changes yet; narrow the mismatch using diagnostics appropriate to a modern JDK, IntelliJ/VS Code and build tooling. In this lesson's **CompletableFuture** example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Concurrency and I/O exercise changes the conditions.

## Tempting shortcuts that weaken CompletableFuture

### Treating CompletableFuture as syntax instead of behavior
If you can reproduce the syntax but cannot predict the state after it runs, the lesson is not finished. Rewrite the example in your own words and name the input, operation and observable result.

### Copying a configuration from a different version
Java tooling evolves. Compare the documentation version, runtime/tool version and project settings before assuming that a screenshot or command from another environment applies unchanged.

### Verifying only the happy path
A successful first run proves one path. Add at least one negative or boundary case relevant to CompletableFuture. The failure should be intentional and the diagnostic should make sense.

### Hiding the important state behind too much abstraction
Abstraction is useful after the behavior is understood. During the first implementation of CompletableFuture, keep the decisive state and control flow visible enough to debug.

## A practical diagnostic path for CompletableFuture

Use this order when CompletableFuture does not behave as expected:

1. Reproduce the smallest failing case.
2. Confirm the actual version/toolchain/environment.
3. Capture the first meaningful diagnostic or unexpected value.
4. Verify identity, permissions and configuration if the operation crosses a service boundary.
5. Inspect intermediate state rather than only the final UI.
6. Change one variable and rerun.
7. Compare the corrected behavior with a negative case.
8. Record the final cause so the same failure is faster to diagnose next time.

## Practice: change the constraint

Extend the worked scenario so that **CompletableFuture** must handle one additional real constraint. Choose one: a second data shape, a failed dependency, an invalid input, a permission difference, a repeat operation, or a larger workload. Before implementing the change, write down the behavior you expect and the evidence that will prove it.

Your result is complete when another learner can reproduce the change from your notes, observe the expected behavior, and intentionally trigger at least one documented failure without damaging their environment. Keep this point tied to **CompletableFuture**. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Concurrency and I/O lesson are specific to this mechanism.

## Review questions for CompletableFuture

- Can you define **CompletableFuture** without using the exact wording of an API/reference page?
- Can you identify the boundary where CompletableFuture begins and where another concept takes over?
- Can you predict the result of the worked example before running it?
- Can you explain one failure from evidence rather than guessing?
- Can you name one production constraint that the beginner example intentionally simplifies?
- Can you repeat the example from a clean state?

## The durable ideas from CompletableFuture

- **CompletableFuture** is useful because it controls observable behavior, not because it adds another piece of syntax to memorize.
- Verification belongs in the workflow: build/check, run/reproduce, inspect, challenge, and repeat.
- The Concurrency and I/O module uses this lesson as a foundation for the next decisions in the Java learning path.
- Official documentation is the source of truth for version-specific contracts; tutorials should teach you how to read and apply those contracts.

## Reference documentation

The following primary documentation was used as a factual reference map for this lesson. ScrutnLearn's explanation is original synthesis rather than copied documentation prose.

- [Dev.java Learn](https://dev.java/learn/)
- [JDBC tutorial](https://docs.oracle.com/javase/tutorial/jdbc/)
- [Java SE API documentation](https://docs.oracle.com/en/java/javase/)
- [Maven guides](https://maven.apache.org/guides/)
- [OpenJDK](https://openjdk.org/)