i bet with some one and he is saying that its on .net or java bt i thought it is ROR or may be in some other language.
its RoR based.It might be possible they have used other technologies
RoR is past. They use Scala
The Twitter Web interface uses the Ruby on Rails framework, deployed on a performance enhanced Ruby Enterprise Edition implementation of Ruby.
As of April 6, 2011, Twitter engineers confirmed they had switched away from their Ruby on Rails search-stack, to a Java server they call Blender.
From spring 2007 to 2008 the messages were handled by a Ruby persistent queue server called Starling, but since 2009 implementation has been gradually replaced with software written in Scala.
The service's application programming interface (API) allows other web services and applications to integrate with Twitter.
Recently they shifted to Ruby on Rails.
@Amit when was that? Their last blog post about the making of their mobile web app is the only time I have seen them mention Rails.
Twitter was initially developed on Rails. The front end is still Rails. They had to do some middle-ware replacements a while back to scale. Google ‘rails twitter’ for more history.
I know Twitter was develop in 2 weeks using Rails. Increasing traffic and their venturing into new areas ‘required’ that they change from Rails, at least according to their statement. I don’t think they will have about 30% Ruby code in their entire app.
thank you every one.
Amardeep Singh wrote in post #1068888:
i bet with some one and he is saying that its on .net or java bt i
it is ROR or may be in some other language.
So I wonder, how many times are we going to resurrect this dead horse so
we can begin the beatings all over again?
Twitter dropped Rails so Rails must suck right?
Never mind that Twitter's situation is a particularly bad example to use
for judging a web application framework. Firstly, it was a long time ago
when they had to make the decision to move to other technologies. Rails
has come a long way since that time. Secondly, Twitter is much more than
just a web site. Their scaling needs are a lot different than the
scaling needs of a typical web application. And finally, there are
plenty of other successful, high profile, sites that are much better
suited for judging whether Rails would be a good choice for the web site
that you want to build.