Seeing these numbers (although as the author states, the data needs to be taken with a grain of salt since he didn't try to set up a more "proper" test environment) really makes me want to take a serious look at vert.x, but what you mention here is my main concern.

Node is a joy to use because of the NPM, and all the available libraries. I'd hate to lose that.

That said, so long as it has a solid websocket api, and I can do routing in it like I would express, I'd give this framework a shot

> Node is a joy to use because of the NPM, and all the available libraries. I'd hate to lose that.

Maven's not bad at all (from a consumption perspective--from a dev perspective, it's a bit of a pain in the ass), and it looks like pretty much any Java library that doesn't do anything too insane should work just fine. (Disclaimer: never used vert.x myself, but I did a quick scan of the code.)

Cool, thanks for the tip

Vert.x leverages the JVM so I don't think library support is really going to be much of a problem. Far from it.

Agreed, it would be good to have CommonJS support.

However, it's unlikely that node modules will work as is with Vert.x, since the API is different. (Unless someone writes a translation layer)