1

The beauty of fast paced frameworks like Rails is that it allows you to deploy quickly- sometimes that comes with a price of having to find ways to scale later. Twitter seem to still be having problems scaling, even though they have been working on this problem for well over a year.

I was wondering - what is preventing them from scaling properly? Is it rails? Database problems? API complexity? Monkeys in the data center?

Any ideas?

Che Kofif
  • 831
  • 1
  • 8
  • 22
  • 3
    I blame Justin Bieber and the spam bots. – BoltClock Sep 09 '10 at 07:29
  • Isn't this going to be pretty much speculation / guessswork and not really an answerable programming question? Unless any twitter developers want to spill the beans here... – serg10 Sep 09 '10 at 07:48
  • I think it's a interresting question about scalability, and I expect to see some architecture tips about how to handle such a scalability problems that happens even with basic application. Everyone can build a twitter in a short amount of time that handles one up to fifty people. I think only few could do so for millions up to infinite. I would be definitely interrested to have information about it. – Larry Sep 09 '10 at 07:54
  • 1
    Serg - of course this is guesswork and not a programming question. But informed guess work can lead to interesting conclusions. – Che Kofif Sep 09 '10 at 09:30

0 Answers0