Re:Vert.x (JVM async) vs Node.js Http benchmarks results
by rapala on Wednesday May 09, 2012 @11:18AM
(#3948951)
Ah, but is Vert.x web scale?
[ Parent
| on HN ]
Re:Vert.x (JVM async) vs Node.js Http benchmarks results
by mikeheath on Wednesday May 09, 2012 @12:19PM
(#3949242)
I realize you're probably joking (at least, I hope so) but just to talk to the scalability point, I've had much better success scaling Netty (which Vert.x is built on) than Node. I've been able to scale Netty to more concurrent connections and Netty performs much better under load than Node. Just my experience.
Re:Vert.x (JVM async) vs Node.js Http benchmarks results
by wickedchicken on Wednesday May 09, 2012 @12:20PM
(#3949248)
> Ah, but is Vert.x web scale?
Better write a Mongo-backed fibonacci generator to check.
Re:Vert.x (JVM async) vs Node.js Http benchmarks results
by purplefox on Wednesday May 09, 2012 @01:25PM
(#3949565)
If you read the docs we specifically mention the "Fibonacci" farce.
Vert.x (unlike node) does not force you to do everything on the event loop. It has a hybrid model.
For things like long running calculations (e.g. Fibonacci) or calling blocking APIs, we support running them on a background thread pool so you don't end up doing stupid things on an event loop which are not appropriate for it.