Just to add some context, Micronaut 4 supports VTs (via the blocking scheduler), while Quarkus runs on Vert.x, which in turn runs on Netty. There’s also Helidon

Just to add some context, Micronaut 4 supports VTs (via the blocking scheduler), while Quarkus runs on Vert.x, which in turn runs on Netty. There’s also Helidon, in which Nima has become an alternative to Netty as a server. This topic was also discussed by the Spring/VMware guys behind Reactor and Spring WebFlux, which also runs on Netty rather than Tomcat. So in this scope it’s interesting to see how JDBC and Tomcat adapt to VTs. In the end, asynchrony and fibers are different perspectives at concurrency management. What I hope is that most people use them as complementary approaches. Lots of companies have used blocking Tomcat underneath and we’re content with it. With VTs they just got a free opt-in performance upgrade. Reactive streams have been perceived by many community members as something overly complicated. So VTs will most likely be warmly welcomed as soon as they trickle through to the production code bases. Most of the team leads I spoke with recently expressed a happy grin when talking about VTs in the context of their blocking codebases.