Comments on: QCon London 2009: Upgrading Twitter without service disruptions

By: Across Weirdish Wild Space » Blog Archive » Software evolution and initial assumptions

Sat, 02 May 2009 14:12:18 +0000

[...] Software evolution and initial assumptions “A very interesting observation during the talk was that Twitter started up with a CMS model and that they gradually moved towards a messaging model. I’ve seen this in a few applications so far, including a casino system, where the messaging model seems to fit best an application intended to power massive community of online users, it seems regardless of what the application actually does business wise. Applications start out completely different, but then more and more functionality gets bolted on top of user messaging capabilities that the whole architecture on the end gets refactored to utilise the messaging channels as the core information transport.” – from Gojko Adzic » Upgrading Twitter without service disruptions [...]

By: Scaling Twitter: Making Twitter 10000 Percent Faster | Unix Stuff

Scaling Twitter: Making Twitter 10000 Percent Faster | Unix Stuff — Thu, 19 Mar 2009 05:50:36 +0000

[...] process, 3 levels of cache, and moved their middleware to a mixture C and Scala/JVM. Update 3: Upgrading Twitter without service disruptions by Gojko Adzic. Lots of good updates on the new Twitter architecture. Update 2: a commenter in [...]

By: Mike Perham

Mike Perham — Wed, 18 Mar 2009 22:57:53 +0000

He was talking about the Ruby’s garbage collection, not Java’s.

By: Shaun

Shaun — Mon, 16 Mar 2009 23:22:06 +0000

I had no idea Twitter started with a CMS model, have to find out more about that!