3 ms·

But at the same time, layering FP with a home rolled static type checking server (??) is bug prone Clearly the home rolled stuff is working out for facebook. T

• Xorlev 13y ago
  Twitter might have some legacy Rails hanging around, but it's a beastly Scala system these days.
• vidarh 13y ago
  Twitter could have been written in any language and worked, but given their old architecture decisions, they'd been just as likely to mess it up in every language. They blamed RoR a lot because they needed an explanation for their problems, but "many to many" messaging even at their scale is a "solved" problem and has been for decades and is fairly easy to scale. (Think of Twitter as a bunch of mailing lists and mailboxes; you scale it by decomposing it: map accounts to virtual "buckets" that becomes the domain part, and map tweets to messages; break apart large follower lists into smaller ones and introduce a forwarding reflector; break apart large following lists by splitting "mailboxes" and doing zipper merges on reading it; add a caching layer -- this is not rocket science, and you could do it properly in any language) Note: I think RoR was a horrible choice for them, though I love Ruby, but I also don't for a second believe RoR was their real problem. Edit: Your overall point stands, though. Especially given that Facebook is a far more complicated application.