News for hackers. Stuff that matters.
Re:Web Framework Benchmarks Round 4 by bjhoops1 on Thursday May 02, 2013 @11:39AM (#5645195)
Really. I've recently been getting into node/express after years of Java, and these results make me feel a whole lot less cool.
Re:Web Framework Benchmarks Round 4 by exabrial on Thursday May 02, 2013 @11:46AM (#5645238)
Well no matter what you use, you should always benchmark for that exact reason. Making things go fast takes a lot of performance engineering, and the JVM has millions of dollars worth of tuning put into it.

BTW, if you like Node.js, you should probably look at Vert.x. I haven't used it, but it's a similar concept, it runs on the JVM, and it seems to spank Node.js.

Re:Web Framework Benchmarks Round 4 by tlear on Thursday May 02, 2013 @12:08PM (#5645394)
When you benchmark Vert.x on a multicore system vs 1 node process. Now add multiple node processes to occupy the cores and store changes completely
Re:Web Framework Benchmarks Round 4 by aphyr on Thursday May 02, 2013 @01:49PM (#5646102)
Indeed. Node's IPC costs are orders of magnitude slower than Java's volatile or atomic datatypes. I would only choose Node for stateless or trivially parallelizable problems--e.g., those where I could push the state problem into a runtime with real threads.

http://aphyr.com/posts/244-context-switches-and-serializatio...

Re:Web Framework Benchmarks Round 4 by qw on Thursday May 02, 2013 @03:02PM (#5646483)
The benchmark is using multiple Node processes.
Re:Web Framework Benchmarks Round 4 by axlerunner on Thursday May 02, 2013 @11:46AM (#5645239)
I got on the Node thing for awhile too, but went back to Java/JBoss/Tomcat/Spring. If you are skilled with the Java stack it is hard to beat for performance and breadth. If you are not, well, I admit the learning curve is steep.
Re:Web Framework Benchmarks Round 4 by bjhoops1 on Thursday May 02, 2013 @04:14PM (#5646922)
I definitely agree for large applications.

But for quickly spinning up a few light service endpoints, Node can't be beat. Especially if you are using JSON-based persistence like MongoDB or CouchDB, using JSON all the way from database to the client is a huge win. I get tired of writing lots of JAXB POJOs to map my JSON objects to and from, especially early on in development when those definitions change rapidly. That's why enjoy using Node, especially for "toy" projects. Less boilerplate and more productive quickly.

Side note: I find myself wishing Node had Annotations and AOP... one of Java's coolest (though oft-misused) features IMHO.

Re:Web Framework Benchmarks Round 4 by tensor on Friday May 03, 2013 @01:16AM (#5648939)
You should look into clojure/compojure. You can get higher performance and write even less code.
Re:Web Framework Benchmarks Round 4 by oberhamsi on Thursday May 02, 2013 @11:56AM (#5645318)
try our RingoJs: it's JS on the JVM. Scripting Java with JavaScript.
Re:Web Framework Benchmarks Round 4 by bjhoops1 on Thursday May 02, 2013 @04:03PM (#5646862)
This, just in case noobs were not confused enough by Java/JavaScript? :)
Re:Web Framework Benchmarks Round 4 by oberhamsi on Friday May 03, 2013 @03:44AM (#5649274)
confusing but accurate :)

The ability to script Java is one of Ringo's killer features - for this benchmark, for example, we dropped in two jars (JDBC myqlconnector & connection pooling from apachecommons) and glued them together with 10 LOC of JS.