# Structured concurrency Published articles for Structured concurrency. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Java 27 Delivers Post-Quantum Cryptography, Future Language Innovation, Helidon 27, JavaFX 27 DevFeed: [Java 27 Delivers Post-Quantum Cryptography, Future Language Innovation, Helidon 27, JavaFX 27]() Original publisher: [Read original article]() Author: Michael Redlich Published: 2026-09-16T10:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Java](), [java-27](), [Post-quantum cryptography](), [Cryptography](), [Security](), [Programming](), [releases]() Tags: [application-security](), [architecture-design](), [cryptography](), [development](), [digital-signature](), [helidon](), [java](), [java-27](), [java27-released](), [javafx](), [jdk-27](), [jdk-28](), [lattice](), [module](), [news](), [oracle](), [portfolio](), [post-quantum-cryptography](), [preview](), [project-valhalla](), [quantum-computing](), [release](), [security](), [structured-concurrency](), [vector]() ### AI overview Oracle released Java 27, the second non-LTS release since JDK 25. Its final feature set contains nine JEPs, including post-quantum hybrid key exchange for TLS 1.3, structured concurrency, compact object headers, JFR data redaction, the Vector API, and PEM encodings for cryptographic objects. Five features remain in preview or incubator stages. ### Source excerpt Oracle has released version 27 of the Java programming language and virtual machine. As the second non-LTS release since JDK 25, the final feature set includes nine JEPs, five of which are still progressing through the preview and incubator stages. This release focuses on strengthening security, future language innovation, and projects under the auspices of the Java Verified Portfolio. By Michael Redlich ## Java 27 Reaches GA With The G1 Garbage Collector By Default Everywhere DevFeed: [Java 27 Reaches GA With The G1 Garbage Collector By Default Everywhere]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-15T13:39:00Z Content type: news Language: en Sources: [Phoronix]() Topics: [Java](), [openjdk](), [releases](), [Concurrency](), [Post-Quantum](), [TLS (Transport Layer Security)]() Tags: [availability](), [concurrency](), [desktop-linux](), [java](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [openjdk](), [phoronix](), [phoronix-test-suite](), [post-quantum](), [release](), [structured-concurrency](), [tls](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview OpenJDK 27 has reached general availability. Its G1 garbage collector is now enabled by default across environments, replacing Serial as the default in constrained environments after improvements in throughput, latency, and memory usage. The release also includes post-quantum hybrid key exchange for TLS 1.3, preview features for lazy constants and structured concurrency, compact object headers by default, and an incubating Vector API. ### Source excerpt Oracle christened Java 27 today with the OpenJDK 27 release reaching general availability (GA) status... ## Coroutine Essentials DevFeed: [Coroutine Essentials]() Original publisher: [Read original article]() Author: author@typealias.com (Dave Leeds) Published: 2026-08-21T00:00:00Z Content type: tutorial Language: en Sources: [Dave Leeds on Kotlin - typealias.com]() Topics: [Coroutines](), [Kotlin](), [coding](), [Software]() Tags: [async](), [cancellation](), [coding](), [concurrency](), [coroutine](), [coroutines](), [deferred](), [dispatcher](), [exception-handling](), [introduction](), [job](), [kotlin](), [launch](), [learn-to-program](), [parallelism](), [programming](), [runblocking](), [software](), [structured-concurrency](), [suspend-function](), [withcontext](), [yield]() ### AI overview This tutorial introduces essential Kotlin coroutine concepts for performing multiple tasks concurrently, such as making network calls while updating a screen. It aims to provide a foundation for day-to-day coding and more advanced coroutine concepts. ### Source excerpt When you're on hold during a phone call, you might also check your email. While brewing coffee, you might also cook breakfast. And while driving a car, you might listen to a podcast. In the same way, sometimes it's helpful for the software that we write to do more than one thing at a time. For example, it could make two or three network calls at one time--all while updating the screen to show the progress of each call. ## Structured Concurrency DevFeed: [Structured Concurrency]() Original publisher: [Read original article]() Published: 2026-04-13T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Structured concurrency](), [Coroutines](), [kotlin-coroutines](), [Concurrency](), [Error Handling]() Tags: [coroutines](), [error-handling](), [guide](), [kotlin](), [memory-leaks](), [processes](), [structured-concurrency](), [workshop-learning-programming]() ### AI overview A Kotlin-focused guide to structured concurrency explains how coroutine hierarchies establish ownership and completion guarantees. It covers cancellation of child coroutines, avoiding unnecessary work and resource leaks, awaiting completion, and handling errors. ### Source excerpt The only guide to structured concurrency you'll ever need. ## How Kotlin influenced Java's development and future DevFeed: [How Kotlin influenced Java's development and future]() Original publisher: [Read original article]() Published: 2026-04-06T00:00:00Z Content type: opinion Language: en Sources: [Kt. Academy]() Topics: [Java](), [Kotlin](), [Development](), [Android](), [Jetpack Compose](), [Scala](), [Groovy]() Tags: [android](), [coroutines](), [development](), [groovy](), [java](), [javascript](), [jetpack-compose](), [kotlin](), [scala](), [structured-concurrency](), [typescript](), [workshop-learning-programming]() ### AI overview This video transcript argues that Kotlin's growth, especially in Android and backend development, pressured Java to evolve. It compares Kotlin's interoperability, tooling, and developer appeal with Java's newer features, while concluding that Java is improving rather than doomed. ### Source excerpt How Kotlin woke Java up, and what it means for the future of Java development. ## From error-handling to structured concurrency DevFeed: [From error-handling to structured concurrency]() Original publisher: [Read original article]() Author: Nelson Elhage Published: 2026-03-23T15:30:00Z Content type: opinion Language: en Sources: [Nelson Elhage]() Topics: [Concurrency](), [Concurrent Programming](), [Error Handling](), [Exception]() Tags: [concurrency](), [error-handling](), [examples](), [exception](), [exception-handling](), [structured-concurrency]() ### AI overview This article examines how error-handling patterns based on stack unwinding and cleanup should be adapted for concurrent programs with multiple tasks. It introduces the problem of unhandled errors in concurrent execution and compares possible behaviors when one task fails. ### Source excerpt How should we think about error-handling in concurrent programs? In single-threaded programs, we've mostly converged on a standard pattern, with a diverse zoo of implementations and concrete patterns. When an error occurs, it is propagated up the stack until we find a stack frame which is prepared to handle it. As we do so, we unwind the stack frames in-order, giving each frame the opportunity to clean up or destroy resources as appropriate. ## How to Prevent Race Conditions in Coroutines DevFeed: [How to Prevent Race Conditions in Coroutines]() Original publisher: [Read original article]() Author: author@typealias.com (Dave Leeds) Published: 2025-11-24T00:00:00Z Content type: tutorial Language: en Sources: [Dave Leeds on Kotlin - typealias.com]() Topics: [Coroutines](), [kotlin-coroutines](), [Kotlin](), [Concurrency]() Tags: [actor](), [atomicint](), [atomics](), [concurrency](), [coroutine](), [coroutines](), [how-to](), [kotlin](), [kotlin-coroutines](), [limitedparallelism](), [mutex](), [programming](), [race-condition](), [shared-mutable-state](), [state](), [stateflow](), [structured-concurrency]() ### AI overview This tutorial explains that Kotlin coroutines and structured concurrency do not automatically protect shared mutable state from race conditions. It introduces the issue using an example that creates 100,000 random bakery orders. ### Source excerpt Thanks to structured concurrency, there are a lot of concerns that we don't have to handle manually when working with Kotlin coroutines. For example, parent coroutines automatically wait for their children to complete before completing themselves. And when a parent coroutine is cancelled, its children are automatically cancelled, too. But when it comes to shared mutable state - mutable data that multiple coroutines could update at the same time - there's nothing magical in the design of coroutines to ensure that the state is updated properly. ## Use Swift with Temporal DevFeed: [Use Swift with Temporal]() Original publisher: [Read original article]() Author: Shy Ruparel Published: 2025-11-10T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [Swift](), [SDKs](), [async/await](), [Swift 6.2](), [Concurrency](), [distributed-systems]() Tags: [announcements](), [async](), [await](), [concurrency](), [github](), [grpc](), [sdk](), [structured-concurrency](), [swift](), [swift-6-2]() ### AI overview Temporal announces a Swift SDK for building durable, fault-tolerant, long-running workflows with Swift 6.2, async/await, and structured concurrency. The SDK supports automatic handling of failures, retries, persistence, and crash recovery, and integrates with Temporal through Swift C interop and gRPC-swift. ### Source excerpt Announcing the Swift Temporal SDK. Build durable, fault-tolerant Workflows in Swift 6.2 with async/await and structured concurrency. ## Announcing Apollo iOS 2.0 DevFeed: [Announcing Apollo iOS 2.0]() Original publisher: [Read original article]() Author: Anthony Miller Published: 2025-10-07T07:00:46Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [Swift](), [GraphQL](), [iOS](), [Concurrency](), [WebSocket]() Tags: [announcement](), [apple](), [concurrency](), [graphql](), [release](), [structured-concurrency](), [swift](), [websocket]() ### AI overview Apollo iOS 2.0 is a release of Apollo's Swift client rebuilt around Swift's modern concurrency model. It introduces concurrency-aware APIs, streamlined layers, and updated platform and distribution requirements, including the retirement of CocoaPods support. GraphQL subscriptions currently support HTTP only; WebSocket support is planned for a future minor release. ### Source excerpt Apollo iOS 2.0 is here, and it's the biggest reimagining of our Swift client yet. Built from the ground up for Swift's modern concurrency model, this release delivers snappier performance, stronger type guarantees, and a cleaner developer experience for teams shipping GraphQL-powered apps across Apple platforms. Improved APIs Swift's structured concurrency and the / syntax weren't just sugar, they introduced an entirely new mental model for reasoning about work, isolation, and cancellation. ## Kotlin Coroutines and Swift DevFeed: [Kotlin Coroutines and Swift]() Original publisher: [Read original article]() Published: 2025-09-15T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [kotlin-coroutines](), [Swift](), [Kotlin Multiplatform](), [Structured concurrency](), [async/await](), [kotlin-flow](), [kotlin-native](), [iOS]() Tags: [async](), [cancellation](), [coroutines](), [how-to](), [kotlin](), [kotlin-flow](), [kotlin-multiplatform](), [kotlin-native](), [structured-concurrency](), [swift](), [workshop-learning-programming]() ### AI overview This tutorial explains how to bridge Kotlin Coroutines and Swift's async/await and structured concurrency in Kotlin Multiplatform iOS projects. It covers suspending functions, exception conversion, Kotlin Flow to AsyncSequence, and calling Swift async functions from Kotlin. ### Source excerpt How to use Kotlin Coroutines in Swift projects, or Swift libraries from Kotlin Coroutines. ## Flash cards for Coroutines - KotlinFlashKards DevFeed: [Flash cards for Coroutines - KotlinFlashKards]() Original publisher: [Read original article]() Published: 2024-09-18T17:50:02Z Content type: tutorial Language: en Sources: [maiatoday]() Topics: [Coroutines](), [Kotlin](), [kotlin-coroutines](), [ide](), [Deadlock](), [Error Handling](), [Testing]() Tags: [code](), [coroutines](), [error-handling](), [flash-cards](), [ide](), [jetbrains](), [kotlin](), [kotlinflashkards](), [structured-concurrency](), [testing]() ### AI overview An in-IDE flash-card course called KotlinFlashKards helps learners practise Kotlin coroutines through questions, hints, code snippets, and tests. It covers basics, structured concurrency, error handling, and testing, and runs through the JetBrains Academy plugin. ### Source excerpt I made something. I made a set of flash cards to practise and learn Kotlin coroutines. I call them KotlinFlashKards (with a K of course). This is the first of a series covering different topics. Why create flash cards? Does this happen to you? You are writing some code, you know something is possible but you can't remember exactly how to do it. By the time you have asked an AI or researched you have forgotten what it was you wanted to do in the first place. There is a way to fix this. Learn and remember the key concepts you use often. One way to do this is to use flash cards. I learnt this from the book The Programmers Brain by Felienne Hermans How does it work? The deck doesn't replace the docs or a good book. It is an in IDE course in the form of a question, a hint that hides the answer and a code snippet with a test to explain the concept. It has four sections Basics - 18 cards Structured Concurrency - 12 cards Error handling - 7 cards Testing - 6 cards You can explore the sections in order or dip in and try tasks at random. Strategies to get the best out of the course? Repeat at regular intervals - Memories are built up if you repeat the flash cards at regular intervals. It is better to do a few lessons more often than to do many lessons in one sitting. You can do the course many times or choose which areas to practise. Recall the answer before peeking - It is important to try to recall the syntax first before looking at the hints or letting the IDE help you. This means you practise your recall of the memory. Think about the solution - For each question and answer you will remember it better too if you think of a practical place where you could use similar code. How do I get it? You need: a JetBrains IDE like Android Studio or Intellij Community edition the JetBrains Acadamy plugin installed Then do the following: Before opening a project click on the Learn menu item on the left Click on New course In the Marketplace search for KotlinFlashKards and start the cou ## Job and children awaiting in Kotlin Coroutines DevFeed: [Job and children awaiting in Kotlin Coroutines]() Original publisher: [Read original article]() Published: 2024-07-15T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Job](), [kotlin-coroutines](), [Structured concurrency](), [cancellation]() Tags: [cancellation](), [job](), [kotlin-coroutines](), [structured-concurrency](), [workshop-learning-programming]() ### AI overview This tutorial explains the Kotlin Coroutines Job context. It describes how each coroutine has its own Job, how parent-child Job relationships support structured concurrency, and how Jobs enable cancellation, completion waiting, and exception handling within a coroutine scope. ### Source excerpt What Job is and how it is the most important context responsible for structured concurrency. ## Key advantages of Kotlin Coroutines DevFeed: [Key advantages of Kotlin Coroutines]() Original publisher: [Read original article]() Published: 2024-06-10T00:00:00Z Content type: article Language: en Sources: [Kt. Academy]() Topics: [Coroutines](), [Kotlin](), [kotlin-coroutines](), [Structured concurrency](), [Concurrency](), [cancellation](), [Testing](), [async/await](), [Ktor](), [Back end](), [Android](), [WebSocket]() Tags: [cancellation](), [concurrency](), [coroutines](), [http](), [kotlin](), [kotlin-coroutines](), [ktor](), [structured-concurrency](), [testing](), [workshop-learning-programming]() ### AI overview This article explains the main advantages of Kotlin Coroutines: simpler imperative-style asynchronous code, structured concurrency, lighter execution than threads, cancellation, synchronization, and precise virtual-time testing. It discusses applications in Android and backend development, including Ktor. ### Source excerpt Where Kotlin Coroutines shine and why you should use them. ## Zero downtime deployment with Arrow and Ktor Native DevFeed: [Zero downtime deployment with Arrow and Ktor Native]() Original publisher: [Read original article]() Author: Simon Vergauwen Published: 2023-02-16T00:00:00Z Content type: tutorial Language: en Sources: [nomisRev]() Topics: [Ktor](), [Deployment](), [zero downtime deployment](), [Coroutines](), [Kubernetes](), [Concurrent Programming](), [Kotlin](), [Microservice]() Tags: [concurrency](), [coroutines](), [deployment](), [kotlin](), [ktor](), [kubernetes](), [microservices](), [resource](), [structured-concurrency](), [structuredconcurrency](), [zero-downtime-deployment]() ### AI overview A webinar explains zero-downtime deployment for functional microservices using Ktor and Kubernetes. It also covers structured concurrency, Arrow's Resource DSL, and KotlinX Coroutines for resource safety and complex use cases. ### Source excerpt Webinar with Anton Arhipov on functional microservices with Ktor and Kubernetes about zero-downtime deployments. ## Graceful Shutdown with Structured Concurrency DevFeed: [Graceful Shutdown with Structured Concurrency]() Original publisher: [Read original article]() Author: Simon Vergauwen Published: 2022-11-24T00:00:00Z Content type: article Language: en Sources: [nomisRev]() Topics: [Concurrency](), [Concurrent Programming](), [Processes]() Tags: [applications](), [concurrency](), [kotlin](), [parallel](), [resource](), [structured-concurrency](), [structuredconcurrency]() ### AI overview This talk explains how structured concurrency can help reason about graceful application shutdown, concurrency, and parallel processes. It discusses issues that can arise when applications do not shut down gracefully. ### Source excerpt In the modern world we often need to make strong guarantees about how our applications terminate; Structured Concurrency gives us a powerful tool to reason about concurrency, parallel processes and how they relate to each other. ## Advanced Swift, fifth edition DevFeed: [Advanced Swift, fifth edition]() Original publisher: [Read original article]() Author: Ole Begemann Published: 2022-03-28T14:03:30Z Content type: release Language: en Sources: [Ole Begemann]() Topics: [Swift](), [Concurrency](), [async/await]() Tags: [async](), [await](), [concurrency](), [generics](), [release](), [structured-concurrency](), [swift]() ### AI overview The fifth edition of Advanced Swift has been released. It is updated for Swift 5.6, adds a chapter on concurrency covering async/await, structured concurrency, and actors, and includes new material on property wrappers, result builders, protocols, and generics. The print edition is now a hardcover, and ebook owners receive a free update. ### Source excerpt We released the fifth edition of our book Advanced Swift a few days ago. You can buy the ebook on the objc.io site. The hardcover print edition is printed and sold by Amazon (amazon.com, amazon.co.uk, amazon.de). Highlights of the new edition: Fully updated for Swift 5.6 A new Concurrency chapter covering async/await, structured concurrency, and actors New content on property wrappers, result builders, protocols, and generics The print edition is now a hardcover (for the same price) Free update for owners of the ebook A growing book for a growing language Updating the book always turns out to be more work than I expect. Swift has grown substantially since our last release (for Swift 5.0), and the size of the book reflects this. The fifth edition is 76 % longer than the first edition from 2016. This time, we barely stayed under 1 million characters: Character counts of Advanced Swift editions from 2016-2022. Many thanks to our editor, Natalye, for reading all this and improving our Dutch/German dialect of English. Hardcover For the first time, the print edition comes in hardcover (for the same price). Being able to offer this makes me very happy. The hardcover book looks much better and is more likely to stay open when laid flat on a table. We also increased the page size from 15x23 cm (6x9 in) to 18x25 cm (7x10 in) to keep the page count manageable (Amazon's print on demand service limits hardcover books to 550 pages). I hope you enjoy the new edition. If you decide to buy the book or if you bought it in the past, thank you very much! And if you're willing to write a review on Amazon, we'd appreciate it. ## Constructing a coroutine scope DevFeed: [Constructing a coroutine scope]() Original publisher: [Read original article]() Published: 2021-10-13T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [kotlin-coroutines](), [Structured concurrency](), [Back end]() Tags: [coroutine](), [kotlin](), [logging](), [scope](), [structured-concurrency](), [workshop-learning-programming]() ### AI overview A tutorial on constructing Kotlin coroutine scopes for Android and backend code. It recommends holding a scope in a property, explains when a custom scope is needed, and discusses dispatchers, supervision, and exception handling. ### Source excerpt How we generally define coroutine scope on Android and on the backend. ## 7 common mistakes you might be making when using Kotlin Coroutines DevFeed: [7 common mistakes you might be making when using Kotlin Coroutines]() Original publisher: [Read original article]() Author: Lukas Lechner Published: 2021-01-08T11:12:53Z Content type: tutorial Language: en Sources: [Lukas Lechner]() Topics: [Coroutines](), [kotlin-coroutines](), [Kotlin](), [Concurrency]() Tags: [allgemein](), [allgemein-kotlin](), [asynchronous](), [concurrency](), [concurrent](), [coroutine](), [coroutines](), [kotlin](), [kotlin-coroutines](), [mistakes](), [structured-concurrency]() ### AI overview A tutorial on common mistakes when using Kotlin Coroutines, including creating a separate Job that breaks structured concurrency and installing SupervisorJob incorrectly. It explains how coroutine scope cancellation and job hierarchies affect cancellation behavior. ### Source excerpt In my opinion, Kotlin Coroutines really simplify the way we write asynchronous and concurrent code. However, I identified some common mistakes that many developers make when using Coroutines. This way, our Coroutine now is cancelled when the Scope is cancelled: The suspend functions in the Kotlin standard library (like e.g. `delay()`) are all cooperative regarding Read More The post 7 common mistakes you might be making when using Kotlin Coroutines first appeared on Lukas Lechner. ## Structured Concurrency Anniversary DevFeed: [Structured Concurrency Anniversary]() Original publisher: [Read original article]() Author: Roman Elizarov Published: 2019-09-28T15:02:02Z Content type: article Language: en Sources: [Stories by Roman Elizarov on Medium]() Topics: [Concurrency](), [Kotlin](), [Coroutines](), [kotlin-coroutines](), [Android](), [reactive](), [Documentation]() Tags: [android](), [asynchronous](), [code](), [concurrency](), [coroutine](), [coroutines](), [documentation](), [kotlin](), [kotlin-coroutines](), [programming](), [reactive](), [reactive-streams](), [structured-concurrency]() ### AI overview This retrospective examines the first year of Structured Concurrency in Kotlin Coroutines. It describes its origins in backend asynchronous programming, adoption in Android lifecycle-aware development, and its role in Kotlin Flows and reactive streams. ### Source excerpt Photo by Annie Spratt on Unsplash A little over a year ago I announced big conceptual shift in the design of Kotlin Coroutines called Structured Concurrency. From that moment on, it took our team about a month to make the first stable 1.0.0 release of kotlinx.coroutines library. After a year of further work, kotlinx.coroutines had added stable support for cold flows that integrate nicely with reactive streams. The library had reached version 1.3.2 by now. It is good time to look back and see how it all worked out -- what was great, what could be improved. Structured Concurrency accomplished more than we hoped for. Originally, the design of structured concurrency was based on the woes experienced by backend developers trying to implement all sorts of asynchronous and concurrent logic. It was focused on making sure that you cannot ever lose a running coroutine or an exception. The key building block we added back then is coroutineScope { ... } function, which encapsulates concurrent operations and limits their scope to the scope of the current call. There was not much else to it, so our recommendation to UI developers was to implement CoroutineScope interface in various "closeable" entities of their applications. We envisioned a simple picture with a simple scope hierarchy. It turned out to be more elaborate in practice. Structured Concurrency was rapidly adopted by Android, which has quite complicated life-cycles. Android libraries added extensions like lifecycleScope and viewModelScope, enabling concise and safe integration of coroutines with those concepts. It became apparent that code looks clearer when an object encapsulating the scope is separate from the rest of code. Introductory Android Codelab on Coroutines recommends defining coroutine scope like this: private val scope = CoroutineScope(...) Nowadays, this style increasingly looks more appealing, so it's time to adjust our documentation to reflect it. At the same time, structured concurrency laid a solid fou