<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>David Rice - Latest Comments in The Magical Fail Whale</title><link>http://davidjrice.disqus.com/</link><description></description><atom:link href="https://davidjrice.disqus.com/the_magical_fail_whale/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 24 Jun 2008 14:20:00 -0000</lastBuildDate><item><title>Re: The Magical Fail Whale</title><link>http://davidjrice.co.uk/2008/06/24/the-magical-fail-whale.html#comment-16104594</link><description>&lt;p&gt;Stephen, I don't think you're on crack. Agile Methodologies are great but when you don't apply good Domain Modeling to the problem at the same time you end up with a solution that works... until you realise there's a problem, in a lot of cases it may already be too late. In that vein I like to think for a good while of the simplest AND most sensible solution.&lt;/p&gt;&lt;p&gt;I don't think there are any other rails apps with scaling problems as big as twitter, all of 37signals products are "naturally sharded" by account/user structure. Campfire did require a part to be swapped out of Rails, the backend that responds to the Javascript polling, the (simply) rewrote it in C.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Rice</dc:creator><pubDate>Tue, 24 Jun 2008 14:20:00 -0000</pubDate></item><item><title>Re: The Magical Fail Whale</title><link>http://davidjrice.co.uk/2008/06/24/the-magical-fail-whale.html#comment-16104591</link><description>&lt;p&gt;Stephen,—&lt;/p&gt;&lt;p&gt;The Twitter problem could be described as being as a result of an agile approach, but I can't really agree with is being as a weakness.&lt;/p&gt;&lt;p&gt;From what I've heard, the original app was built and launched in 6 weeks.  Now that's pretty agile.&lt;/p&gt;&lt;p&gt;The scaling issues are twofold:&lt;br&gt;Scaling anything requires two things:&lt;br&gt;1) The NEED to scale&lt;br&gt;2) a scaleable architecture&lt;br&gt;3) $$$ to pay for that architecture&lt;/p&gt;&lt;p&gt;Twitter was a fast, cheap job that took off, and took off big.  The risk was minimal.  A thousand Twitters could have launched on the same day and if they flopped, not a lot would have been lost.&lt;/p&gt;&lt;p&gt;Twitter did take off, and very soon, as Dave rightly says, they found themselves with a platform that wasn't designed to do what Twitter users ultimately started doing: sending messages, having conversations.&lt;/p&gt;&lt;p&gt;I'm willing to bet, that had they invested in scaleable architecture first, and built their system from the ground up as a distributed messaging platform, then none of us would ever have got the service, they probably still wouldn't be launched and they wouldn't stand a chance.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Campbell</dc:creator><pubDate>Tue, 24 Jun 2008 14:11:00 -0000</pubDate></item><item><title>Re: The Magical Fail Whale</title><link>http://davidjrice.co.uk/2008/06/24/the-magical-fail-whale.html#comment-16104588</link><description>&lt;p&gt;Twitter folk were admitted that they architected Twitter like a content management system when it should have been a messaging system.&lt;/p&gt;&lt;p&gt;As I have to work with Rendezvous every day and see millions of messages passing, I have to wonder....&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mj</dc:creator><pubDate>Tue, 24 Jun 2008 13:58:00 -0000</pubDate></item><item><title>Re: The Magical Fail Whale</title><link>http://davidjrice.co.uk/2008/06/24/the-magical-fail-whale.html#comment-16104585</link><description>&lt;p&gt;I wonder if the problems Twitter has (and some 37Signals apps) are more related to weaknesses in current implementations of Agile Methodologies than anything else?&lt;/p&gt;&lt;p&gt;JF said that Campfire is AJAX based and not Comet because they just wanted "to get things done", or be Agile. And a similar situation seems to be at the root of Twitter's problems.&lt;/p&gt;&lt;p&gt;Or maybe I'm on crack?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stephen</dc:creator><pubDate>Tue, 24 Jun 2008 13:54:00 -0000</pubDate></item></channel></rss>