I know Twitter initially ran on the Ruby on Rails platform.
Is this true today?
+8
A:
Twitter has a very strange architecture. They started out on Rails but now it's a combination of Rails and Scala. They started replacing some of the backend functionality with Scala to get access to the JVM, but many of the pages are still served with Rails today.
Unfortunately Rails has gotten a bit of a reputation for not being scalable enough due to Twitter moving away from it. This is (in my opinion) a bad misconception - the problem Twitter was having was with long-running processes and with green threads (which don't use the OS threads). Also, how many applications have 300 million+ users?
Jaco Pretorius
2010-09-24 07:14:44
More specifically, the Message Queueing server was moved to Scala.
Swanand
2010-09-24 07:50:32
+1 for this "Also, how many applications have 300 million+ users?"
tony_le_montana
2010-09-24 11:34:41
A:
1 )twitter forms use
*CSRF (Cross Site Request Forgery): like rails
2 )twitter is a REST application : like rails
'They started out on Rails but now it's a combination of Rails and Scala' and a big chunk of javascript
It 's (thin MVC + big javascript ) concept ,like gmail
germanlinux
2010-09-24 09:43:48
You make Twitter sound like a malicious application when you say CSRF.
BoltClock
2010-09-24 09:48:40
no, rails use an Cross Site Request Forgery PROTECTION ,a token in every form.
germanlinux
2010-09-24 12:41:47