Intermediate vs Terminal Operations

Every stream operation is either intermediate or terminal. An intermediate operation, such as filter or map, returns a new stream, so more operations can be chained after it. A terminal operation, such as toList or count, produces a result (or a side effect) and ends the stream. Knowing which is which explains why a pipeline without a terminal operation does nothing at all. In this lesson, you will learn the differences and the full list of each kind.

Differences Between Intermediate and Terminal Operations

Intermediate Operations

Terminal Operations

Example: A Pipeline Without a Terminal Operation

Let's see an example that proves intermediate operations wait for a terminal one.

import java.util.List;
import java.util.stream.Stream;
 
public class NothingHappens {
    public static void main(String[] args) {
        List<String> names = List.of("Navika", "Srihitha", "Advitha");
 
        Stream<String> pipeline = names.stream()
            .filter(n -> {
                System.out.println("  filter " + n);
                return n.length() > 6;
            });
        System.out.println("Pipeline built, nothing printed yet");
 
        long count = pipeline.count();
        System.out.println("Count: " + count);
    }
}

Pipeline built, nothing printed yet
  filter Navika
  filter Srihitha
  filter Advitha
Count: 2

Explanation: Building the pipeline with filter printed nothing, because intermediate operations are lazy. Only when count() (a terminal operation) ran did the elements flow through the filter.

Example: Short-Circuiting Terminal Operations

Some terminal operations stop as soon as they know the answer:

import java.util.List;
 
public class ShortCircuit {
    public static void main(String[] args) {
        List<Integer> marks = List.of(91, 38, 85, 42);
 
        System.out.println("Any fail? "
            + marks.stream().anyMatch(m -> m < 40));
        System.out.println("All pass? "
            + marks.stream().allMatch(m -> m >= 40));
        System.out.println("None above 100? "
            + marks.stream().noneMatch(m -> m > 100));
        System.out.println("First above 80: "
            + marks.stream().filter(m -> m > 80).findFirst().get());
    }
}

Any fail? true
All pass? false
None above 100? true
First above 80: 91

Explanation: anyMatch stops at 38, the first failing mark. allMatch also stops at 38, because one failure is enough to answer "no". findFirst stops at 91 without looking further.

Common Mistakes

Building a pipeline and forgetting the terminal operation. Nothing runs.

Using peek to change data. It's for looking only; use map to transform.

Calling get() on the Optional from findFirst without checking. It throws if the stream was empty.

Interview Corner

Practice

1. Easy: Classify each as intermediate or terminal: limit, max, distinct, collect, skip, anyMatch.
2. Harder: Add peek calls to a pipeline of filter, map and findFirst and print what passes each stage. Explain why only some elements are printed.

Key Takeaways