Re:Vert.x (JVM async) vs Node.js Http benchmarks results
by spullara on Wednesday May 09, 2012 @12:50PM
(#3949400)
Since they are not limited by a single threaded VM, you would run those using the worker pools and communicate with them via an actor type model similar to erlang. So, modulo a small amount of verticle code to deploy your image processor, yes.
Re:Vert.x (JVM async) vs Node.js Http benchmarks results
by simpsond on Wednesday May 09, 2012 @12:55PM
(#3949423)
Not automagically, but java has some really good tools for helping. See the http://docs.oracle.com/javase/7/docs/api/java/util/concurren... package. Check the Executors section and you can easily distribute work via threads to all your cores. In fact, vert.x is using netty, which makes heavy use of threads along with async IO. You can do both.
Assumed I use this ImageIO package. Will it be nonblocking, concurrent and spread to all my cores automagically with Vert.x??