Structured Concurrency in Java 21: What It Fixes and Why It Exists

Note This series uses the Java 21 preview API for structured concurrency ( StructuredTaskScope , JEP 453). The API evolved in later previews. See Part 9 for Java 21 -> Java 25 migration guidance. Compile and run with --enable-preview . Originally published on engnotes.dev: Introduction to Structured Concurrency in Java 21 This is a shortened version with the same core code and takeaways. The annoying part of concurrent request code is usually not starting work in parallel. Java has had plenty of ways to do that for years. The real mess shows up later. One task fails. Another keeps running. Cancellation is inconsistent. Cleanup is half in one method and half somewhere else. That is the problem structured concurrency is trying to fix. The Old Shape This is a very normal baseline from the project: CompletableFuture < String > cf1 = CompletableFuture . supplyAsync (() -> simulateService ( "Service-A" , 200 )); CompletableFuture < String > cf2 = CompletableFuture . supplyAsync (() -> simula