Kotlin coroutines have been around since 2017 and have contributed to defending the usage of Kotlin in everything from Android development to multi-platform, to developing highly available and resilient services making optimized use of resources, and allowing threads to be available as soon as possible. The use of coroutines also implicated the usage of context and scopes, which for many became complicated abstract concepts. And then Java 21 was released in 2023 and while researching and applying this at work I realized that in some places, it makes sense to remove the usage of coroutines and replace them with virtual threads. On the other hand, in other places, the usage of Kotlin coroutines seems to remain justified.
In this session I will talk about funny examples and real-life problems that I found on the field, why did they occurred, and how I solved them. We may find a common ground between Java Virtual Threads and Kotlin Coroutines, or maybe not.
After this session, you will come out with a different understanding of what Kotlin Coroutines and Java Virtual Threads have to offer. You'll be able to make better-informed decisions on how both work, so that you can independently suggest solutions in your team, at work, or on your own time.

This session has examples and may introduce some live code running examples. However code may be shown during the presentation, there is no expectation to make live code changes.