Java Virtual Threads - Reactive Programming Killer?

To improve the scalability of applications, Java developers write complex Reactive Pipelines using Completable Futures or Spring WebFlux. However, with the release of Java 21 and Virtual Threads - this is no longer necessary. This talk explains the reason why Reactive programming was born and why Virtual Threads may eventually kill it.

Check out my other links below for discounted popular courses (12.99$ or best local price)

[viraj_shetty]

Hi All - Use link below for my popular Java courses.

[MoshlehuddinMazumder]

Very precise explanation. Kudos! Would love to see some work around migrating from Spring webflux to virtual thread.

[mgfxfwd]

Great explanation! Thank you for taking the time to do this

[daveamiana]

I enjoyed the explanation. Thank you for putting out this content; really helped me wrap my head around this concept.

[akshaykapadia]

Do we need additional config to use virtual threads in spring boot project when we upgrade to java 21?

[MrKKPA]

How is the memory allocation of the objects used with carrier threads?

[wdeath]

Data process and real time data processing, will define how we make our applications.
Its not just the async, reactive programming is about data processing in pipelines.
I think betting on data is always safe, before some years we didn't even have data-engineers now they are everywhere, this will come to software also.

[duybuiha]

Hi Viraj, should we refactor reactive code style to synchronize code and upgrade spring webflux to virtual thread? Is there something reactive can do and do better than virtual thread? r2dbc, callback event ?, stream composition and transformation ?, Thanks.

[goumuk]

Thank you for the beautiful explanations. I want to understand thread life cycle in reactive programming in a more deeper way. Is there any resource I can refer to?

[GodofStories]

Excellent presentation, really explained it well.

[amitbhattacharyya]

That's the first thought came in my mind when I came across virtual thread, however on 8:08, fully reactive design do you mean future and completablefuture can you point to some git repo for better understanding to active reactive design in java 8 for example

[szrmbjr]

Great video. Pretty sure never learned so much in just 13 mins 😉

[sambaemol]

Thank you very much. You made it look so easy.

[manuyaji]

Hi Viraj,
I had a question.
The reason why we simply don't scale the number of platform threads in our application is because it consumes ~1 MB per thread.

How does having virtual threads solve that problem?

[MartinCrazyProgrammer]

But, is this so easy? Cause I can not believe that Java team would kill Webflux so easy just with this virtual threads, that is weird...

[khalidhamid]

Why not switch to Kotlin instead, it has coroutines (structured concurrency), flows ( reactive pipelines), it’s not verbose as Java, first class support out of Spring, interoperable with Java libraries, don’t need Lombok, you can leverage KSP for faster compilation or to write plugins, you can use functional style programming with Arrow library, small learning curve plus once you get use to it you can write your own DSL.

I did Java for a decade then Kotlin now again Java. It’s just feels like I’m going backwards when doing Java.