Modern Java: Streams, Lambdas & Optional
Functional programming arrived in Java with Streams and Lambdas. Write clean, declarative data pipelines without messy nested for-loops.
Featured Developer Sponsor • Zero-Token Protection
📋 Copy Java Streams & Functional Pipelines Snippet
import java.util.*;
import java.util.stream.Collectors;
List<String> names = List.of("Steve", "Alex", "Steve", "Zombie", "Enderman");
// Deduplicate, filter, transform, and collect into unmodifiable list
List<String> filtered = names.stream()
.distinct()
.filter(name -> name.length() > 4)
.map(String::toUpperCase)
.sorted()
.collect(Collectors.toUnmodifiableList());
// Grouping and frequency counting
Map<Integer, Long> countByLength = names.stream()
.collect(Collectors.groupingBy(String::length, Collectors.counting()));⚠️ 5 Fatal Traps & Engineering Pitfalls
Trap #1: Re-Using an Already Consumed Stream
A Java Stream can only be operated upon once. Calling a terminal operation (e.g.
.collect() or .count()) closes the stream; invoking another operation on the same stream instance throws IllegalStateException: stream has already been operated upon or closed.Trap #2: Side-Effects Inside Intermediate Stream Operations
Mutating external state inside
.map() or .filter() violates functional purity. When executed on a parallelStream(), concurrent modifications result in non-deterministic race conditions and lost data.Trap #3: Blindly Using parallelStream() on Small Collections
Parallel streams introduce thread splitting, scheduling on the common ForkJoinPool, and result merging overhead. For collections under 10,000 items, parallel streams are frequently 5x to 10x slower than standard sequential streams.
Trap #4: Calling Optional.get() Without isPresent() Verification
Calling
opt.get() directly when a value is empty throws NoSuchElementException, reproducing the exact problem that Optional was invented to prevent. Use opt.orElse(defaultValue) or opt.orElseThrow().Trap #5: Unbounded Infinite Streams Without limit()
Creating an infinite stream using
Stream.iterate(0, i -> i + 1) without chaining .limit(n) before a terminal collection operation causes an infinite loop that rapidly exhausts all JVM heap memory.💬 Frequently Asked Questions
Sponsored Utility
While You're Here
Sponsored Recommendations
Advertisement