Ok Ok Ok... first off, I apologize for the sliiightly misleading
subject line. But, I thought I'd try to draw some attention and see if
I could get some discussion going (hopefully no flames though!).
I was browsing around and I came across this interview with Alex Payne
from twitter:
http://www.radicalbehavior.com/5-question-interview-with-twitter-developer-alex-payneThe second interview question is what particularly drew my attention
where he says that they have been running into a number of scaling
issues that they probably wouldn't have with other frameworks.
There are three main points that caught my attention in the response.
1) "At this point in time there's no facility in Rails to talk to more
than one database at a time."
2) "setting up multiple read-only slave databases [is not a quick fix
to implement]"
3) Ruby + Rails' syntactical sugar = slow
Point #3 is pretty well known, the solutions always mentioned before
is scale out. However, Alex says that they can't because of 1 & 2.
I've been under the impression (and still am) that doing 1 & 2 really
isn't that hard.
So, the question is, what to do if you have a rails app and are in
twitters place?
-carl
--
EPA Rating: 3000 Lines of Code / Gallon (of coffee)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk@...
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe@...
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en-~----------~----~----~----~------~----~------~--~---
