home.social

#structuredconcurrency — Public Fediverse posts

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

fetched live
  1. Adding an LLM is easy. Building a reliable AI system isn't. Damiana Nascimento shows how Spring AI and Java 26 simplify orchestration, concurrency and observability for production AI.

    Discover how to build AI into your architecture: javapro.io/2026/08/13/building

    #Java #SpringAI #LLM #VirtualThreads #StructuredConcurrency

  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. Ever seen requests fail while subtasks kept running anyway? That’s one of the nastiest problems in concurrent systems — especially with #VirtualThreads. Babneet Singh maps out how #StructuredConcurrency in #Java26 adds clear task ownership & teardown: javapro.io/2026/06/09/structur

  4. Still handling cancellation, timeouts & fallback logic manually across concurrent tasks? That’s usually where distributed systems become unpredictable under load.
    Babneet Singh breaks down how #StructuredConcurrency changes the runtime model in #Java26: javapro.io/2026/06/09/structur

  5. Ever seen requests fail while subtasks kept running anyway? That’s one of the nastiest problems in concurrent systems — especially with #VirtualThreads. Babneet Singh maps out how #StructuredConcurrency in #Java26 adds clear task ownership & teardown: javapro.io/2026/06/09/structur

  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. “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

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

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

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

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

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

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

  16. 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

  17. #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

  18. #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

  19. 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

  20. #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

  21. #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

  22. Forget “Hello World.” Java just said “Goodbye Boilerplate.” @ronveen takes you on a tour where classes vanish, imports simplify, and main() becomes human.
    Is #Java still Java?

    Go read: javapro.io/2025/06/17/modern-j

    #VirtualThreads #ProjectLoom #PatternMatching #StructuredConcurrency