15 ms·
+1 to this, reactive programming is a major pain in my ass. With virtual threads there’s no longer a need for them.
by kapperchino 3y ago
+1 to this, reactive programming is a major pain in my ass. With virtual threads there’s no longer a need for them.
- p2detar 3y agoIn general yes, but FWIW measurements point out that reactive vert.x seems to handle saturation much better. (1) Also, vert.x are already exploring how to adapt to the new threads model. (2) 1 - https://gist.github.com/vietj/fe9f886d489853ab07111ba5715b13ee https://gist.github.com/vietj/fe9f886d489853ab07111ba5715b13... 2 - https://vertx.io/blog/vertx-virtual-threads-incubator/ https://vertx.io/blog/vertx-virtual-threads-incubator/
- Lightbody 3y agoJust curious -- have you personally confirmed this? Not trying to cast doubt... just noting that I have exactly the same feelings (hopes?) but I have yet to personally confirm it, in large part because it's not yet fully GA so we haven't jumped in with our production workloads.