3 ms·
There's also another option for doing async on the JVM: http://vertx.io/ http://vertx.io/ The polyglot aspect, very impressive performance (as it's based on ne
by RyanZAG 13y ago
There's also another option for doing async on the JVM: http://vertx.io/ http://vertx.io/
The polyglot aspect, very impressive performance (as it's based on netty), and simple deployment model make it an interesting choice. It let's you put computationally intensive operations into worker verticles that run in their own thread pool, while also having i/o blocking operations run async on the event loop in a nodejs style.
- pron 13y agoYep, it's just that I find that these solutions (Node.js and Vertx.io) make you adopt a functional/callback-based style not because it's appropriate from a design perspective, but rather to work around OS limitations. Fibers first remove the problem, and then let you choose the most appropriate programming style for your domain.