home.social

#structuredconcurrency — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #structuredconcurrency, aggregated by home.social.

  1. “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: javapro.io/2026/05/06/java-26-

    @openjdk

  2. “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: javapro.io/2026/05/06/java-26-

    @openjdk

  3. 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: javapro.io/2026/01/28/how-to-d
    via @hannotify & Bram Janssens

    #Java25

  4. 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: javapro.io/2026/01/28/how-to-d
    via @hannotify & Bram Janssens

    #Java25

  5. #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: javapro.io/2026/02/19/virtual-

    #Java

  6. #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: javapro.io/2026/02/19/virtual-

    #Java

  7. 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: javapro.io/2026/01/28/how-to-d
    via @hannotify & Bram Janssens

    #Java25

  8. 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: javapro.io/2026/01/28/how-to-d
    via @hannotify & Bram Janssens

    #Java25

  9. 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?

    #Python #Trio #StructuredConcurrency

  10. 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?

    #Python #Trio #StructuredConcurrency

  11. 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?

    #Python #Trio #StructuredConcurrency

  12. 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?

    #Python #Trio #StructuredConcurrency

  13. 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?

    #Python #Trio #StructuredConcurrency

  14. #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?

    Read more: javapro.io/2025/12/23/java-25-

    #Java #JVM #StructuredConcurrency

  15. #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?

    Read more: javapro.io/2025/12/23/java-25-

    #Java #JVM #StructuredConcurrency

  16. Still making sequential remote calls even with #VirtualThreads? @chwoerz explains how StructuredTaskScope cuts latency by running tasks concurrently—without reactive complexity. Curious how it works?

    Dive in: javapro.io/2025/12/23/java-25-

    #Java #Java25 #JVM #StructuredConcurrency

  17. Still making sequential remote calls even with #VirtualThreads? @chwoerz explains how StructuredTaskScope cuts latency by running tasks concurrently—without reactive complexity. Curious how it works?

    Dive in: javapro.io/2025/12/23/java-25-

    #Java #Java25 #JVM #StructuredConcurrency

  18. Still making sequential remote calls even with #VirtualThreads? @chwoerz explains how StructuredTaskScope cuts latency by running tasks concurrently—without reactive complexity. Curious how it works?

    Dive in: javapro.io/2025/12/23/java-25-

    #Java #Java25 #JVM #StructuredConcurrency

  19. Now double at #JCON Berlin: the new #JAVAPRO issue AND our “30 Years of #Java” edition! Featuring #Java25, #VirtualThreads, #StructuredConcurrency & #GenAI.
    Stop by & grab your free copies!

    Can’t attend? Download or subscribe: javapro.io/2025/10/28/stay-upd

  20. Now double at #JCON Berlin: the new #JAVAPRO issue AND our “30 Years of #Java” edition! Featuring #Java25, #VirtualThreads, #StructuredConcurrency & #GenAI.
    Stop by & grab your free copies!

    Can’t attend? Download or subscribe: javapro.io/2025/10/28/stay-upd

  21. #StructuredConcurrency aims to make concurrent code readable and safe. But how does it compare to CompletableFuture? Merlin Bögershausen dives into #Java21’s latest preview features.

    Deep insights + code → javapro.io/2025/07/22/more-act

    #VirtualThreads #Concurrency #JVM @openjdk

  22. #StructuredConcurrency aims to make concurrent code readable and safe. But how does it compare to CompletableFuture? Merlin Bögershausen dives into #Java21’s latest preview features.

    Deep insights + code → javapro.io/2025/07/22/more-act

    #VirtualThreads #Concurrency #JVM @openjdk

  23. Nebenläufigkeit in #Java war oft mit Komplexität und Overhead verbunden. #Java21 bricht mit alten Konzepten und bringt Werkzeuge wie #StructuredConcurrency.

    Lese im Artikel von Merlin Bögershausen, wie Sie damit Ihre Projekte modernisieren: javapro.io/de/mehr-action-mehr

    @openjdk

  24. Nebenläufigkeit in #Java war oft mit Komplexität und Overhead verbunden. #Java21 bricht mit alten Konzepten und bringt Werkzeuge wie #StructuredConcurrency.

    Lese im Artikel von Merlin Bögershausen, wie Sie damit Ihre Projekte modernisieren: javapro.io/de/mehr-action-mehr

    @openjdk

  25. #Java 21 introduces #VirtualThreads, but the real shift lies deeper: #StructuredConcurrency & Scoped Values redefine how we write parallel code. Merlin Bögershausen breaks it down — with live code examples.

    Read his #JAVAPRO aritcle now → javapro.io/2025/07/22/more-act

    #JVM @openjdk

  26. #Java 21 introduces #VirtualThreads, but the real shift lies deeper: #StructuredConcurrency & Scoped Values redefine how we write parallel code. Merlin Bögershausen breaks it down — with live code examples.

    Read his #JAVAPRO aritcle now → javapro.io/2025/07/22/more-act

    #JVM @openjdk

  27. #Java 25 may redefine StructuredTaskScope before it goes final. Until then, developers face a moving target—with clear benefits & shifting syntax. Ron Veen outlines the state of #StructuredConcurrency.

    In depth: javapro.io/2025/04/18/structur

    #ProjectLoom #API #Multithreading

  28. #Java 25 may redefine StructuredTaskScope before it goes final. Until then, developers face a moving target—with clear benefits & shifting syntax. Ron Veen outlines the state of #StructuredConcurrency.

    In depth: javapro.io/2025/04/18/structur

    #ProjectLoom #API #Multithreading

  29. Can #VirtualThreads really replace platform threads — at scale? Merlin Bögershausen examines new #Java21 #Concurrency #APIs, from StructuredTaskScope to lightweight threading.

    Find out what actually changes → javapro.io/2025/07/22/more-act

    #JVM #StructuredConcurrency @openjdk

  30. Can #VirtualThreads really replace platform threads — at scale? Merlin Bögershausen examines new #Java21 #Concurrency #APIs, from StructuredTaskScope to lightweight threading.

    Find out what actually changes → javapro.io/2025/07/22/more-act

    #JVM #StructuredConcurrency @openjdk

  31. #Java’s #Concurrency model has evolved: from Thread to ExecutorService to #VirtualThreads & Scoped Values. Merlin Bögershausen explains what matters in #Java21 — and why old patterns may hold you back.

    Full article → javapro.io/2025/07/22/more-act

    #JVM #StructuredConcurrency @openjdk

  32. #Java’s #Concurrency model has evolved: from Thread to ExecutorService to #VirtualThreads & Scoped Values. Merlin Bögershausen explains what matters in #Java21 — and why old patterns may hold you back.

    Full article → javapro.io/2025/07/22/more-act

    #JVM #StructuredConcurrency @openjdk

  33. #Java now streams with memory, discards threads instead of pooling & runs without public static void main. #VirtualThreads, Gatherers & no-boilerplate coding—@ronveen breaks down the quiet revolution

    Read: javapro.io/2025/06/17/modern-j

    #ModernJava #ProjectLoom #StructuredConcurrency

  34. #Java now streams with memory, discards threads instead of pooling & runs without public static void main. #VirtualThreads, Gatherers & no-boilerplate coding—@ronveen breaks down the quiet revolution

    Read: javapro.io/2025/06/17/modern-j

    #ModernJava #ProjectLoom #StructuredConcurrency