Twitter is also particularly notorious for blaming Rails when it is/was blatantly obvious their architecture at the time was a total mess. Including using Rails for stuff that should have been factored out into a separate shared-nothing backend service regardless of the frontend language/framework. They could have rewritten in pretty much anything and made it faster/more reliable.

I've spent more than 2 seconds on Google for this topic. This StackOverflow post[1] was actually very informative. See the answer by Jörg W Mittag, specifically this quote:

>>In several interviews, the Twitter developers have pointed out that Ruby on Rails was not responsible for their scaling problems. On the contrary, only the maintainability of Ruby made it possible to do such large-scale architectural changes to fix their scaling problems.

Then again, that seems to have been written in 2010. I'm sure things changed since then.

http://stackoverflow.com/questions/3514633/do-ruby-on-rails-...

Do you have a reference for this? I did a Google search for "yellow pages rails node", but it turns up your comment as the #1 result.