Maybe I didn't make myself clear. My point was that their Rails implementation may not be well written, i.e., not architect-ed properly since beginning. You can

Maybe I didn't make myself clear. My point was that their Rails implementation may not be well written, i.e., not architect-ed properly since beginning. You cannot simply throw a few tables and scaffolds and hope it scale. That way may work for small apps, definitely not for web-scale apps like this. To be fair, Node.js also has its own quirks, besides the callback maintenance issues, I also mentioned in another post that Node.js is not as scalable as a lot of people present it to be.