Let’s have a look these three frameworks,
Netty isÂ an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.
And here are some usefulÂ comparisonÂ articles,
- Vert.x: Why the JVM May Put Node.js on the Ropes
- Vert.x vs node.js simple HTTPÂ benchmarks
- Vert.x is much faster than Node.js when reading the same file from the filesystem more than once. Neither Vert.x nor the JVM is doing any explicit caching, so this is most likely due to the OS caching it (memory mapped files?). In a webserver-type app the same file is likely to be served many times so this is pretty significant
- Node.js doesnâ€™t appear to scale particularly well using the `cluster` module. The advice from the node.js folks is not to use it (for now). This leaves node with no out-of-the-box way to scale across multiple coresÂ
- Many of the out of the box load testing tools donâ€™t appear to pipeline very much. The Vert.x results are dramatically better when thereâ€™s a high degree of pipelining going on.
- Java on the JVM is extremely fast. No surprises thereÂ But what is very encouraging is how the other JVM langs held up â€“ in particular Rhino held up very well against V8Â
|Language Type||Dynamic or Static||Dynamic||Static||Dynamic||Dynamic||Static|
|Speed of Development||Fast||Fast||Slow||Fast||Fast||Slow|
|Synchronous Threading Support||Great||None||Great||Poor||Poor||Good|
2 thoughts on “Asynchronous Event-driven Network Application Framework:vert.x, Node.js or Netty”