Vert.x is a framework for the next generation of asynchronous, scalable, concurrent applications, which aims to provide an alternative to Node.js for the JVM.
I can only speak from the one real world vert.x project (version 1.3 I think) developed by someone else that I was left to maintain and improve: The memory usage was ridiculous, the cpu usage was high, it crashed at least once a week, and was difficult to work on.
I replaced it with a nodejs app, with the same functionality. It could handle far more connections with less memory, cpu and did not crash (other than bugs).
Put it down to the old version of vert.x or the fact that the nodejs model is much easier to understand.....
Scaling up nodejs beyond a single node is harder though. (there's an npm module for that though now I'm sure)
The memory usage was ridiculous, the cpu usage was high, it crashed at least once a week, and was difficult to work on.
I replaced it with a nodejs app, with the same functionality. It could handle far more connections with less memory, cpu and did not crash (other than bugs).
Put it down to the old version of vert.x or the fact that the nodejs model is much easier to understand.....
Scaling up nodejs beyond a single node is harder though. (there's an npm module for that though now I'm sure)