Node has captured the attention of early adopters by clearly differentiating itself as being asynchronous from the ground up while remaining accessible. Now that server side JavaScript is at the cutting edge of the asynchronous, real time web, it is in a much better position to establish itself as the go to language for also making synchronous, CRUD webapps and gain a stronger foothold on the server. This talk covers the current state of server side JavaScript beyond Node. It introduces Common Node, a synchronous CommonJS compatibility layer using node-fibers which bridges the gap between the different platforms. We look into Common Node's internals, compare its performance to that of other implementations such as RingoJS and go through some ideal use cases.

1. Server side JavaScript: going all the way #rejectjs 29.09.11

6. Akshell NarwhalJS RingoJS Wakanda GPSEE v8cgi

7. ServerJS Fragmentation

13. Sync vs. Async function add(callback) { http.get(url1, function(response1) { var part1 = response1.data; http.get(url2, function(response2) { var part2 = response2.data; callback(part1 + part2); } } }

14. Sync vs. Async http.get(url1).data + http.get(url2).data

21. everything!

27. Node.js process [ closure closure t ->

28. RingoJS (0.8) process thread stack process thread stack t ->

29. Common Node (fibers) process fiber stack fiber stack [ t ->

30. Comparison Node.js Common Node RingoJS Process Count Single Single Multiple State Closure Fiber Stack Thread Stack Multitasking User (co-op) Library (co-op) OS (pre-empt) Memory Usage Low Low High “ Jitter” High High Low

44. Benchmarks ab -n 50000 -c 50

55. Throughput

56. SyncJS Fragmentation