“Can I block here?” With #Java26, the answer is increasingly yes. #VirtualThreads & #StructuredConcurrency reduce the need for callback-heavy code & oversized thread pools.
Damiana Nascimento explains what modern #JVM-first design looks like: https://javapro.io/2026/05/06/java-26-in-practice-how-the-jvm-is-changing-the-way-we-write-code/
ThreadLocal breaks with #VirtualThreads. @chwoerz explains why — and how ScopedValue replaces it with safe, immutable, scope-bound context propagation. Migrating to #Java25?
Read this first: https://javapro.io/2025/12/23/java-25-getting-the-most-out-of-virtual-threads-with-structured-task-scopes-and-scoped-values/
Still fighting thread pools when traffic spikes? #ProjectLoom offers a different path. @BalaRawool shows how #VirtualThreads, #StructuredConcurrency, and Scoped Values work together in a real #SpringBoot app.
See what you can simplify: https://javapro.io/2026/02/19/virtual-threads-structured-concurrency-and-scoped-values-putting-it-all-together/
Thread leakage is the silent killer of “quick parallelization.” #StructuredConcurrency makes sure child tasks end with the parent scope—by design.
Learn the shutdown patterns + how they behave in failure scenarios: https://javapro.io/2026/01/28/how-to-do-structured-concurrency-in-java-25/
via @hannotify & Bram Janssens
#Concurrency bugs rarely fail loudly — they leak resources, stall requests, & waste CPU. @BalaRawool demonstrates how #StructuredConcurrency can short-circuit failures and keep workflows consistent in #SpringBoot.
Make your services more resilient: https://javapro.io/2026/02/19/virtual-threads-structured-concurrency-and-scoped-values-putting-it-all-together/
Still fighting thread pools when traffic spikes? #ProjectLoom offers a different path. @BalaRawool shows how #VirtualThreads, #StructuredConcurrency, and Scoped Values work together in a real #SpringBoot app.
See what you can simplify: https://javapro.io/2026/02/19/virtual-threads-structured-concurrency-and-scoped-values-putting-it-all-together/
Do you still need reactive programming for high throughput? @chwoerz shows how #VirtualThreads + #StructuredConcurrency handle fan-out calls cleanly and synchronously.
See the #Java25 approach & learn more: https://javapro.io/2025/12/23/java-25-getting-the-most-out-of-virtual-threads-with-structured-task-scopes-and-scoped-values/
Thread leakage is the silent killer of “quick parallelization.” #StructuredConcurrency makes sure child tasks end with the parent scope—by design.
Learn the shutdown patterns + how they behave in failure scenarios: https://javapro.io/2026/01/28/how-to-do-structured-concurrency-in-java-25/
via @hannotify & Bram Janssens
Ok, to follow up on yesterday's structured concurrency question:
In Python, I have a hypothetical HTTP client:
async with HTTP() as client:
http.get("https://site.example/index.html")
and it handles things like HTTP/2 multiplexing and connection pools and stuff. So it needs some background tasks to coordinate and maintain them.
Classically, I'd call these "daemon tasks" (after Python's daemon threads).
But I feel like I'm missing something?
#VirtualThreads scale concurrency—but they don’t fix structure or error handling. @chwoerz shows how StructuredTaskScope and ScopedValue complete the picture in #Java25. Want safer, faster concurrent code?
JAVAPRO
AstraLuma #PyConUS