Thanks for the info and your thoughts, Darren. That scalability article -- the whole site, in fact -- is a great resource.
Andreas Darren Boyd wrote: > On Mon, Sep 1, 2008 at 8:48 PM, Andreas Kirn <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > But I don't want this to turn into a religious debate about Rails, so > let me rephrase the question: If one were looking for a Ruby framework > to build a large, high-traffic application, which of the previously > listed frameworks would you recommend and why? > > > If Rails is still in the group of 'previously listed frameworks', than > I would recommend it. I haven't used any of the others, so I can't > offer much of an opinion either way. I've played with Merb and > DataMapper, and I like what I see, but I haven't done anything serious > enough with either of them to form a real opinion (I am planning on > it, for the most part I only lack the time). > > > > > Btw, do you know of any high-traffic social or e-commerce apps > built on > Rails, other than Twitter? > > > > http://rails100.pbwiki.com/Alexa+Rankings > > This is a good read too.. > > http://highscalability.com/friends-sale-architecture-300-million-page-view-month-facebook-ror-app > > I've worked on http://jibjab.com/ and am currently working on > http://msnack.com/. Both are rails sites. JibJab takes some serious > bursty traffic at times (they have good relationships with CNN and Fox > News and few other good sources of viewers). They also deal with a > lot of large uploads, so the problems they face are things like > mongrel starvation. > > mSnack has a lot less web traffic than JibJab (in fact, it has very > little), but there is *a lot* of message delivery activity in the > backend. Believe it or not, it is using Ruby Threads and > ActiveRecord. Trust me, no one was more surprised than me to see it > work; and work fairly well :). > > Of course, a lot of the performance issues we deal with in Ruby-land > are in Ruby itself, not in any of the frameworks. At the end of the > day, scalability comes from decent programmers who understand the code > they commit to source control. > > I can only recommend Rails because I've had success with it. But that > recommendation is only good for me. Ultimately you have to find a > technology that you will be successful with. Good luck :). > > Darren > > > > --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
