Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #9364

I

Ikai Says...

Personal blog · ikaisays.comprogrammingcareerbusiness

Ikai Says... is a personal blog at ikaisays.com about programming, career and business. Since 2009, 8 different Hacker News readers have linked it 12 times, most often “Clearing up some things about LinkedIn mobile’s move from Rails to node.js”. The last post was in 2013, but the archive is still widely read.

Visit the blog
12mentions?
8HN people?
2009–2015first – last linked?
Links on Hacker News per year · peak 6 in 2012

Too few sampled comments (6) to say how often HN recommends it.?

Why HN links it

HN readers link Ikai Lan's blog to add context on LinkedIn's Rails-to-Node mobile server rewrite, App Engine and Riak key design, and a rebuttal of a claim about why Silicon Valley code is bad.

Summarised by Claude from a sample of 6 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

I'm Ikai and I say a lot about the world of technology. This blog contains some of the more interesting ideas I've shared.

Most-linked posts?

  1. Clearing up some things about LinkedIn mobile’s move from Rails to node.js
    3 people · 4 mentions · first linked 2012-10-05
  2. App Engine datastore tip: monotonically increasing values are bad
    2 people · 2 mentions · first linked 2011-01-27

What Hacker News says?

  1. This article actually gives details of their first implementation which suggest that they could cut servers without switching to node : http://ikaisays.com/2012/10/04/clearing-up-some-things-about...

    Comment linking /2012/10/04/clearing-up-some-things-about-linkedin-mobiles-move-from-rails-to-node-js/

    on “LinkedIn Mobile Moved from Rails to Node: 27 Servers Cut and Up to 20x Faster”
  2. Submitted Clearing up some things about LinkedIn mobile’s move from Rails to node.js as a story · 205 points

    HN discussion
  3. I was on the team at LinkedIn when we first wrote the thing on Ruby on Rails. Here's my writeup containing some more context: http://ikaisays.com/2012/10/04/clearing-up-some-things-about... While I'll freely admit v8 is much faster than MRI Ruby, the efficiency gains are likely more related to 1) the rewrite factor 2) moving to non-blocking 3) the fact that the original server ... um, needed love

    Comment linking /2012/10/04/clearing-up-some-things-about-linkedin-mobiles-move-from-rails-to-node-js/

    on “LinkedIn Mobile Moved from Rails to Node: 27 Servers Cut and Up to 20x Faster”
  4. Submitted Twitter, Ruby on Rails, Scala and people who don’t RTFA as a story · 85 points

    HN discussion
  5. Dear boulos: I'm saying this to you but it is a general message to the Google Cloud division. I'm an early GAE adopter, still running a system in it to this day. I've seen your kind come and go many times. Sometimes it's a well-placed engineer, sometimes a technically capable and empowered support rep, an evangelist, something. These people show up in the community, they're empathetic, responsive and openly talk abo…

    Comment linking /

    on “How Amazon took control of the cloud”
  6. Submitted App Engine datastore tip: monotonically increasing values are bad as a story · 11 points

    HN discussion
  7. Be careful with this trick. Although it appears to work well for Riak, it can cause lots of problems for BigTable style stores, like HBase, since it bottlenecks all the writes through one node. See: http://ikaisays.com/2011/01/25/app-engine-datastore-tip-mono... HBase (and I've heard BigTable) work best with purely random row keys - like the author of this post was using initially.

    Comment linking /2011/01/25/app-engine-datastore-tip-monotonically-increasing-values-are-bad/

    on “10x speedup in write performance in Riak Innostore based on keyname”
  8. Submitted Why “The Real Reason Silicon Valley Coders Write Bad Software” is wrong as a story · 3 points

    HN discussion
  9. wasd · 2014-05-13Recommends
    > The old story of linkedin where moving to Node.js from Rails > for their mobile traffic, reducing the number of servers from 30 to 3 >(90% reduction) and the new system was up to 20x faster. It isn't as simple as that. There was a great article from a former linkedin engineer about why the original API server was so slow. [0] [0]: http://ikaisays.com/2012/10/04/clearing-up-some-things-about...

    Comment linking /2012/10/04/clearing-up-some-things-about-linkedin-mobiles-move-from-rails-to-node-js/

    on “Why Node.js is becoming the go-to technology in the Enterprise”
  10. Submitted On Hackathons, Process, Email and the Tragedy of the Commons as a story · 2 points

    HN discussion
  11. This article is wrong. Here's why: http://ikaisays.com/2012/10/09/why-the-real-reason-silicon-v...

    Comment linking /2012/10/09/why-the-real-reason-silicon-valley-coders-write-bad-software-is-wron/

    on “The Real Reason Silicon Valley Coders Write Bad Software”
  12. Submitted On Hackathons, Process, Email and the Tragedy of the Commons as a story · 1 points

    HN discussion

Search all of HN for ikaisays.com