Kotlin Coroutines and Java Virtual Threads are conceptually very similar.
In details and implementation they are different, of course. A good
presentation on comparing coroutines and virtual threads by Urs Peter:
https://www.youtube.com/watch?v=bOLChQ3fFQo
I was just referencing Kotlin
sry I meant executor.
On Fri, 1 Sept 2023, 10:57 bukaj_s, wrote:
> You are confusing coroutines and virtual threads.
> Afaik you can try to use virtual thread pool, question is how much
> synchronization is camel using under the hood.
>
> On Fri, 1 Sept 2023, 10:34 ski n, wrote:
>
>> OK,
You are confusing coroutines and virtual threads.
Afaik you can try to use virtual thread pool, question is how much
synchronization is camel using under the hood.
On Fri, 1 Sept 2023, 10:34 ski n, wrote:
> OK, thanks. It will take some (couple of years) before most libraries are
> catching up.
OK, thanks. It will take some (couple of years) before most libraries are
catching up.
At least, Spring Boot will already support Java 21 with virtual threads in
their next release (
https://spring.io/blog/2023/08/24/spring-boot-3-2-0-m2-available-now). I
don't know exactly how they do it, but
Hi
No plan for virtual threads - this relies on 3rd party libraries and many
other frameworks starting to adopt them as well, which means Java 21 as
minimum base version.
Support for Java 21 is to run on JDK21. JDK17 will be primary supported,
and 21 secondary, that is the plan for this year.
In integration there is a lot of Async I/O (calling disk, databases, api's
and other external systems). Though Camel is very fast, it's mostly these
async I/O calls that take time and eat a lot of platform threads.
For example:
from("direct:start")
.log("some log") //this takes less than 1 ms
