Clearing up some things about LinkedIn mobile’s move from Rails to node.js
1–10 of 33 posts
Re: Clearing up some things about LinkedIn mobile’s move from Rails to node.js
#2And the blog-to-commentary-to-blog cycle begins anew.
Re: Clearing up some things about LinkedIn mobile’s move from Rails to node.js
#3And the blog-to-commentary-to-blog cycle begins anew.
and then come the posts about how they scaled their custom blog backend to cope with the hn front page traffic.
Re: Clearing up some things about LinkedIn mobile’s move from Rails to node.js
#4Re: Clearing up some things about LinkedIn mobile’s move from Rails to node.js
#5This sounds much more sane than "node is 20x faster than rails", thanks for validating the assumption most of us were making.
Re: Clearing up some things about LinkedIn mobile’s move from Rails to node.js
#6This sounds much more sane than "node is 20x faster than rails", thanks for validating the assumption most of us were making.
This. I wish there had been more context in the original article.
Re: Clearing up some things about LinkedIn mobile’s move from Rails to node.js
#7I met Ikai through the Silicon Valley Rails Meetup, which I co-hosted back in 2008-2009 and which met at LinkedIn HQ in Mountain View. This post is a great contribution to the recent discussion about Rails at LinkedIn, and I hope it gets the attention it deserves.
Re: Clearing up some things about LinkedIn mobile’s move from Rails to node.js
#8> And those requirements kept growing. If my calculations are correct, the standard setup for engineers now is a machine with 20 or more gigabytes of RAM just to RUN the software.
Close. In 2011, all the engineer desktops got upgraded to 36Gigs. At the time, the eng department still hadn't figured out how to deploy without duplicating hundreds of jar files everywere.
Re: Clearing up some things about LinkedIn mobile’s move from Rails to node.js
#9> And those requirements kept growing. If my calculations are correct, the standard setup for engineers now is a machine with 20 or more gigabytes of RAM just to RUN the software. Close. In 2011, all the engineer desktops got upgraded to 36Gigs. At the time, the eng department still hadn't figured out how to deploy without duplicating hundreds of jar files everywere.
Hah, I bet all the new engineers were like, SWEET! I get a system with 36 gigs of RAM!
Then their hearts sank when they realized why.
Re: Clearing up some things about LinkedIn mobile’s move from Rails to node.js
#10I met Ikai through the Silicon Valley Rails Meetup, which I co-hosted back in 2008-2009 and which met at LinkedIn HQ in Mountain View. This post is a great contribution to the recent discussion about Rails at LinkedIn, and I hope it gets the attention it deserves.
Hey Michael!
Was there a recent discussion? I'm fairly certain everyone has moved on from Rails, and I'm not sure if they're still using it anywhere at LinkedIn. There are a few folks using JRuby, but I believe they're using Sinatra: