Re:LinkedIn Mobile Moved from Rails to Node: 27 Servers Cut ...
by benbjohnson on Thursday October 04, 2012 @04:00PM
(#4614076)
Can someone update the title to read: "LinkedIn Moved from Server to Client: 27 Servers Cut and Up to 20x Faster"?
[ Parent
| on HN ]
Re:LinkedIn Mobile Moved from Rails to Node: 27 Servers Cut ...
by hnriot on Thursday October 04, 2012 @04:07PM
(#4614109)
But that would be wrong, the server legitiamtely moved from rails to node. Just because node is JavaScript doesn't mean that it automatically runs on the client, JavaScript is a perfectly viable server language too.
The title could be improved by reflecting that this is for LinkedIn mobile, but the rails->node is correct.
Re:LinkedIn Mobile Moved from Rails to Node: 27 Servers Cut ...
by ericf on Thursday October 04, 2012 @04:20PM
(#4614181)
Not wrong, a lot of their performance gains were a result of caching their templates client side and having their servers only return data. That is a much smaller load on the server and easily could account for the reduction in servers. The title makes it sound as if they reduced their servers and increased their performance simply by migrating from ruby to node.