A lot has been said already about Twitter's scalability issues. Many have given Twitter as an anti-pattern of how not to deal with scalability and have suggested different solutions for scaling it. As Twitter is famously a Ruby-on-Rails deployment, this case has also been used as a weapon in the language/platform wars between the RoR and Java camps, and to a lesser degree, also with the LAMP (PHP) camp
Comments
Re: Twitter as a scalability case study
Java? Are you sure?
Re: Twitter as a scalability case study
Not a bad article, but not really about Twitter either. It's not his fault, I just don't think the info is out there, but it seems like a lot of speculation about Twitter, then just follows with the same basic scaling strategies that all the highscalibity.com regulars are familiar with.
I do enjoy the refreshing assertion that it's not the language that matters, but the architecture.
Re: Twitter as a scalability case study
I'm a full believer that languages don't scale, solutions scale. That said, the right framework needs to be put in place at the beginning...otherwise we've seen what happens over and over again. BTW - still loving twitter :)
Post new comment