Re:We switched to Node.js: the good and the not so good
by julien on Monday January 14, 2013 @07:21AM
(#5054339)
Well, we assumed everyone knew about the good... so yes, we're happy with the rewrite and will probably never go back. Also, a 25% saving in servers for us translate in several thousands of dollars saved monthly. Not negligible :)
Re:We switched to Node.js: the good and the not so good
by rartichoke on Monday January 14, 2013 @09:17AM
(#5054695)
Yeah but in your article you said you're not even sure if this is because of node. You made some architectural changes in your code base and hinted that might have been a reason for the speed boost too.
The article might as well be written as "we refactored our code and got a nice speed boost".
Re:We switched to Node.js: the good and the not so good
by octo_t on Monday January 14, 2013 @07:23AM
(#5054345)
How much development time did this cost though, when you could have been adding new features and improving the user experience?
It sounds a bit like you guys rewrote it because node.js is hot and you then stuck with the rewrite because of sunk costs. Or am I imagining things?
Thanks for sharing your experiences with us. I'm just asking those questions because I want to learn more about them.