Java · OOP, JVM and backend craft
How does the Java Streams API work?
Short answer
The Streams API processes collections declaratively through lazy intermediate operations and one terminal operation. It improves readability for transformations but is not automatically faster.
A stream pipeline has a source, zero or more intermediate operations and one terminal operation. Intermediate operations such as filter, map and sorted are lazy. Nothing runs until a terminal operation such as collect, forEach, reduce or count is invoked.
Map<String, List<Employee>> byDepartment =
employees.stream()
.filter(employee -> employee.salary() > 50_000)
.collect(Collectors.groupingBy(Employee::department));Rules for correct use
- A stream can be consumed once; reusing it throws IllegalStateException
- Prefer side-effect-free functions so the pipeline is predictable
- Use primitive streams such as IntStream to avoid boxing overhead
- Parallel streams only help for CPU-bound work on large, splittable sources
- Keep pipelines short enough that a reviewer can follow them
Streams are a readability tool, not a performance guarantee. A simple loop can be faster and clearer for indexed access, early exit or complex control flow. Collectors such as groupingBy, partitioningBy, joining and toMap cover most aggregation needs.
Follow-ups you should expect
Interviewers use these to check whether the first answer was understanding or memorisation.
- 1Which stream operations are lazy?
- 2Why can a stream only be consumed once?
- 3When is a parallel stream a bad idea?
- 4What is the difference between map and flatMap?
Say it in the interview
A stream pipeline starts from a source, applies lazy intermediate operations, and runs when a terminal operation is called. I use it for filter, map and aggregation because it reads well. I keep functions pure and pipelines short. Streams are not automatically faster, and parallel streams can be slower or unsafe for blocking work, so I choose them deliberately rather than by default.
Use this as a model, not a script. Saying it in your own words is what makes it survive follow-up pressure.
Related questions
Reading is step one
Now say it out loud.
Understanding an answer and delivering it under pressure are different skills. Rehearse this topic in a live Java mock interview and get scored feedback on depth, clarity and confidence.