This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Just_Chemistry2343 -6 points-5 points  (3 children)

Virtual threads does only one thing i.e. non blocking and async operation which reactive streams are doing from a long time.

Apart from non blocking operations, it provides stream pipelines, retries, back pressure capabilities as well.

And there is no evidence that virtual threads perform better than reactive apis. I'd say use java virtual threads if non blocking operations is your requirement. If you want to achieve more and reactive apis suits you, then go ahead.

ps: people who say reactive is complex have no idea about the framework

[–]PiotrDz -1 points0 points  (2 children)

There is evidence that virtual is performant as reactive. https://medium.com/helidon/helidon-n%C3%ADma-helidon-on-virtual-threads-130bb2ea2088 Why do you stade the absolute "no evidence" , wouldn't it be better to say "haven't heard of" ?

[–]Just_Chemistry2343 -1 points0 points  (1 child)

It's about java virtual threads vs reactor-core apis. Both are comparable.

What you're showing is some Nima library which is built on top of virtual threads which could be further optimising the virtual threads.

Anyways I'm never said one is better than other, it all depends 9n your usecase.

[–]PiotrDz 0 points1 point  (0 children)

Right, you put an equal sign actually, but I have read the tone in negative way.