findFirst() vs findAny() in Java Streams

Direct Answer

findFirst() returns the first element when the stream has an encounter order; on an unordered stream it may return any element. findAny() deliberately permits any element and is nondeterministic. When any match is acceptable, findAny() gives an implementation more freedom, especially in parallel, but it is not guaranteed to be faster—measure the workload.

Code Example

import java.util.List;
import java.util.Optional;

public class FindFirstVsFindAny {
    public static void main(String[] args) {
        var names = List.of("amy", "bob", "ben", "cat");

        // findFirst: deterministic, respects encounter order
        Optional<String> first = names.stream()
            .filter(n -> n.startsWith("b"))
            .findFirst();           // always "bob"

        // findAny: any match; may differ under parallel()
        Optional<String> any = names.parallelStream()
            .filter(n -> n.startsWith("b"))
            .findAny();             // "bob" or "ben"

        System.out.println(first.get() + " / " + any.get());
    }
}

Common Mistakes & Pitfalls

• Expecting findAny to be stable: A sequential test may appear to return the first element, but that is not its contract. Use findFirst when encounter order matters.
• Assuming every stream is ordered: findFirst can promise a first element only when the stream has an encounter order.
• Claiming a guaranteed speed-up: findAny gives a parallel implementation more freedom, but source splitting, workload, and overhead decide performance. Measure it.
• Ignoring Optional.empty(): Both operations return Optional, so handle the no-result case explicitly.