Intermediate vs Terminal Stream Operations

Direct Answer

Intermediate operations such as filter, map, and sorted return a stream and are lazy: they build the pipeline without starting traversal. A terminal operation such as collect, count, forEach, or findFirst consumes the pipeline and initiates the evaluation needed for its result; a short-circuit terminal operation may stop before visiting every element.

Code Example

import java.util.List;

public class IntermediateVsTerminal {
    public static void main(String[] args) {
        var nums = List.of(1, 2, 3, 4, 5, 6);

        var result = nums.stream()
            .filter(n -> n % 2 == 0)  // intermediate: lazy, returns a Stream
            .map(n -> n * 10)         // intermediate: lazy, returns a Stream
            .toList();                // terminal: triggers execution, returns a List

        System.out.println(result); // [20, 40, 60]
    }
}

Common Mistakes & Pitfalls

• Forgetting the terminal operation: Writing list.stream().filter(x -> x > 10) and expecting filtered results — without collect() or another terminal op, the stream just exists but doesn't execute.
• Trying to reuse a stream: Storing the result of list.stream().filter() in a variable and calling multiple terminal operations on it — the second terminal op throws IllegalStateException because the stream has already been consumed.
• Misclassifying operations: Thinking peek is terminal because it performs an action — it's actually intermediate and requires a terminal operation to execute.