5 ms·

imho, it's rails. rails (and any other ruby framework) is not suited for a real-time communication platform like twitter. also you forgot about messaging queue

• KirinDave 18y ago
  Why would you say that? It's not like the Ruby code is handling that many messages. Even Rails sites don't use ruby for their concurrency and messaging. They push down to a database or to another concurrency level like ActiveMQ. Above them lives another piece of code or hardware to do load balancing. This isn't even about Ruby, it's about the Rails architecture.