Pretty nice, i know that it won't replace the webflux (reactive) and all (non-blocking and back-pressure ) but it is very nice improvement for Java itself.
Is there any value to use virtual threads with webflux applications assuming there is a way to configure netty just like the way you configured tomcat?
Consider a case when you use block to get the value of mono/flux, and do that in a virtual thrrad. You will get the value, but you won't really block anything
Can i use Virtual Thread in every case? Is there any case where i cannot (should not) use Virtual Threads?
ปีที่แล้ว
As always, nice content!!!. I wonder what we can do with those cheaps threads, maybe more connections to a database ? the concept of connection pool would change later?
Thanks that's great I'm very excited to use virtual thread but can we use virtual thread in production or we should wait until spring include this future
Is it fair to say that if tasks being executed within the context of thread is primarily CPU intensive (or doesn't involve any blocking operations), then such task executions will NOT be benefited from virtual threads as eventually you will need an OS thread to execute the thread's core logic ?
Yes, exactly. The benefit of a virtual thread is seen when you do io operations - db calls or other. If you have a huge cpu intensive calculation - the virtual thread has no benefit there, actually a bit of an overhead in that scenario
Forget Spring... plain vanilla Microprofile is more powerful. If you change to Helidon or Quarkus you'll have the cloud native experience, out of the box, that Spring doesn't give you, even jumping through hoops.
Thanks for the tutorial. This is good stuff from DV. Will like to use it in a multi module /microservices application
What a nice and neat tutorial! Thanks
Loving the content
Thanks Dan, I will be stealing these slides to learn my students about VT (most don't even know about threads, so it's a challenge)
Thanks!
How cool! Almost feels too easy! Love the content as always. Your style and delivery make concepts like this super easy to digest.
Could you tell me please what’s ide you are using and which theme? It looks great
Pretty nice, i know that it won't replace the webflux (reactive) and all (non-blocking and back-pressure ) but it is very nice improvement for Java itself.
Thanks for the explanation, I'd like to know what software or tool you did use to create the illustrations about threads. Thanks again.
The idea of Java Virtual Threads was borrowed from Erlang Processes for BEAM virtual machine ))
Kotlin coroutines
where did you get this cool thsirt? =D
Hallelujah...
Is there any value to use virtual threads with webflux applications assuming there is a way to configure netty just like the way you configured tomcat?
Consider a case when you use block to get the value of mono/flux, and do that in a virtual thrrad. You will get the value, but you won't really block anything
NICE T-SHIRT.
Btw do you know if there's any database library that is loom ready ?
Can i use Virtual Thread in every case? Is there any case where i cannot (should not) use Virtual Threads?
As always, nice content!!!. I wonder what we can do with those cheaps threads, maybe more connections to a database ? the concept of connection pool would change later?
good video very informative, can you please make a video about Spring boot event sourcing / CQRS
Thanks that's great I'm very excited to use virtual thread but can we use virtual thread in production or we should wait until spring include this future
@Spring Office Hours thank you
What is the IDE you are using here?
Intellij IDEA I documented my setup here if you're interested > th-cam.com/video/g78is10FjF0/w-d-xo.html
Is it fair to say that if tasks being executed within the context of thread is primarily CPU intensive (or doesn't involve any blocking operations), then such task executions will NOT be benefited from virtual threads as eventually you will need an OS thread to execute the thread's core logic ?
Yes, exactly. The benefit of a virtual thread is seen when you do io operations - db calls or other. If you have a huge cpu intensive calculation - the virtual thread has no benefit there, actually a bit of an overhead in that scenario
173rd...Thanks Dan
Funny, Scala cats has such thing from many years back. Yet it is a preview in java.
Forget Spring... plain vanilla Microprofile is more powerful. If you change to Helidon or Quarkus you'll have the cloud native experience, out of the box, that Spring doesn't give you, even jumping through hoops.