3 ms·
Depends on the traffic you need to work with. I've kept an eye on Node.js for some time. So far, among the failures involved with Node.js are Plurk and SyncPad.
by cygwin98 15y ago
Depends on the traffic you need to work with. I've kept an eye on Node.js for some time. So far, among the failures involved with Node.js are Plurk and SyncPad. Plurk switched to JBoss Netty, while SyncPad used Erlang instead. Though that was almost a year ago, things may have improved.
Not to bad-mouth Node.js here. Just to give some counter examples to anybody who wants to try Node.js in production.
- tszming 15y agoPlurk? Seems they changed from Netty to Node JS, not vice versa?
- simonw 15y agoThey switched back to Netty again: http://amix.dk/blog/post/19577 http://amix.dk/blog/post/19577
- tszming 15y agoThanks for the link. It seems running multiple instance of node.js and use a more updated version would helps (maybe). Anyway, I always think that lack of threading support is definitely a feature instead of incompetency. Threading is hard and average developers should avoid it. (Unless you are doing scientific computing). If you need to scale, eventually you will need multiple servers anyway.