#Nodejs showed us huge performance gains compared to what we were using before, which was Ruby on Rails.” Read more at

Exclusive: How LinkedIn used Node.js and HTML5 to build a better, faster app | VentureBeat

#Nodejs showed us huge performance gains compared to what we were using before, which was Ruby on Rails.” Read more at

This morning, LinkedIn launched its gorgeously overhauled mobile app . We’ve already told you all about the new features, but for developers, the most exciting part is what’s going on under the hood. The app is two to 10 times faster on the client side than its predecessor, and on the server side, it’s using a fraction of the resources, thanks to a switch from Ruby on Rails to Node.js, a server-side JavaScript development technology that’s barely a year old but already rapidly gaining traction. Also, the development time was unusually fast. “It was fast by all standards,” LinkedIn’s mobile development lead Kiran Prasad told VentureBeat. “I’ve worked at startups and big companies like Yahoo, and yeah, it was fast.” Part of the development speed was due to the fact that the team knew ahead of time exactly what needed to be built. “We really, soundly knew what we wanted to do...

Full article: http://venturebeat.com/2011/08/16/linkedin-node/

Tweets

@FriendsOfNodeJS » 18 Aug '12, 3am
RT @webdents: #Nodejs showed us huge performance gains compared to what we were using before, which was Ruby on Rails.” Read more at [link]
@webdents » 18 Aug '12, 3am
#Nodejs showed us huge performance gains compared to what we were using before, which was Ruby on Rails.” Read more at [link]
@adenneulin » 18 Aug '12, 11am
RT @webdents: #Nodejs showed us huge performance gains compared to what we were using before, which was Ruby on Rails.” Read more at [link]
@ismail2ov » 18 Aug '12, 3am
RT @webdents: #Nodejs showed us huge performance gains compared to what we were using before, which was Ruby on Rails.” Read more at [link]
@Youssefyamani » 18 Aug '12, 3am
Nodejs showed us huge performance gains compared to what we were using before, which was Ruby on Rails.” [link]