<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Twitter Downtime On the Upswing</title>
	<atom:link href="http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/</link>
	<description>Startup and Technology News</description>
	<pubDate>Fri, 22 Aug 2008 03:05:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Rama Mamuaya / Media Sosial dan Internet &#187; Pilih Twitter atau Plurk?</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2413111</link>
		<dc:creator>Rama Mamuaya / Media Sosial dan Internet &#187; Pilih Twitter atau Plurk?</dc:creator>
		<pubDate>Sat, 19 Jul 2008 07:48:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2413111</guid>
		<description>[...] banyak pihak yang kecewa dengan kinerja Twitter yang bermasalah dengan downtime yang parah ( hampir sekali sehari ) akhirnya bermunculan &#8220;saingan&#8221; dari Twitter yaitu [...]</description>
		<content:encoded><![CDATA[<p>[...] banyak pihak yang kecewa dengan kinerja Twitter yang bermasalah dengan downtime yang parah ( hampir sekali sehari ) akhirnya bermunculan &#8220;saingan&#8221; dari Twitter yaitu [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Get FriendFeed notifications with imfeeds - smalls blogger</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2396284</link>
		<dc:creator>Get FriendFeed notifications with imfeeds - smalls blogger</dc:creator>
		<pubDate>Thu, 03 Jul 2008 12:36:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2396284</guid>
		<description>[...] FriendFeed meet imfeeds. Imfeeds is a service that lets you get instant messages to your chat client of your RSS feeds as they happen. Imfeeds supports AIM, MSN, Yahoo and Google Talk. Wait, before you ask, yes imfeeds is more reliable than twitter. [...]</description>
		<content:encoded><![CDATA[<p>[...] FriendFeed meet imfeeds. Imfeeds is a service that lets you get instant messages to your chat client of your RSS feeds as they happen. Imfeeds supports AIM, MSN, Yahoo and Google Talk. Wait, before you ask, yes imfeeds is more reliable than twitter. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Telephony 2.0 &#187; Blog Archive &#187; Twitter As &#8216;Global Communications Utility&#8217;? Hang On Now&#8230;</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2388875</link>
		<dc:creator>Telephony 2.0 &#187; Blog Archive &#187; Twitter As &#8216;Global Communications Utility&#8217;? Hang On Now&#8230;</dc:creator>
		<pubDate>Thu, 26 Jun 2008 19:18:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2388875</guid>
		<description>[...] help scaling because despite (or probably more likely because of) its popularity the service has suffered repeated [...]</description>
		<content:encoded><![CDATA[<p>[...] help scaling because despite (or probably more likely because of) its popularity the service has suffered repeated [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitterpitch? &#171; Eric Gonzalez</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2285363</link>
		<dc:creator>Twitterpitch? &#171; Eric Gonzalez</dc:creator>
		<pubDate>Fri, 09 May 2008 18:21:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2285363</guid>
		<description>[...] Mike Arrington: &#8220;Twitter downtime on the upswing&#8221;  DA Howlett: &#8220;.. while Twitter has great utility, it could be so much more&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] Mike Arrington: &#8220;Twitter downtime on the upswing&#8221;  DA Howlett: &#8220;.. while Twitter has great utility, it could be so much more&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TechCrunch en français &#187; Twitter souhaite abandonner Ruby on Rails</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2248398</link>
		<dc:creator>TechCrunch en français &#187; Twitter souhaite abandonner Ruby on Rails</dc:creator>
		<pubDate>Fri, 02 May 2008 08:19:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2248398</guid>
		<description>[...] de nombreuses sources et après deux années de nombreux problèmes de gestion de taille, Twitter prévoit d&#8217;abandonner Ruby on Rails comme framework [...]</description>
		<content:encoded><![CDATA[<p>[...] de nombreuses sources et après deux années de nombreux problèmes de gestion de taille, Twitter prévoit d&#8217;abandonner Ruby on Rails comme framework [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter Said To Be Abandoning Ruby on Rails</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2245579</link>
		<dc:creator>Twitter Said To Be Abandoning Ruby on Rails</dc:creator>
		<pubDate>Thu, 01 May 2008 20:54:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2245579</guid>
		<description>[...] hearing this from multiple sources: After nearly two years of high profile scaling problems, Twitter is planning to abandon Ruby on Rails as their web framework and [...]</description>
		<content:encoded><![CDATA[<p>[...] hearing this from multiple sources: After nearly two years of high profile scaling problems, Twitter is planning to abandon Ruby on Rails as their web framework and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter: Cool but Unreliable? &#124; eyeline.mobi</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2222977</link>
		<dc:creator>Twitter: Cool but Unreliable? &#124; eyeline.mobi</dc:creator>
		<pubDate>Fri, 25 Apr 2008 10:07:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2222977</guid>
		<description>[...] same time I have also started to read more about Twitter. And got upset with news that Twitter is unreliable at [...]</description>
		<content:encoded><![CDATA[<p>[...] same time I have also started to read more about Twitter. And got upset with news that Twitter is unreliable at [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Иван Комаров &#187; Blog Archive &#187; links for 2008-04-24</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2221442</link>
		<dc:creator>Иван Комаров &#187; Blog Archive &#187; links for 2008-04-24</dc:creator>
		<pubDate>Thu, 24 Apr 2008 17:36:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2221442</guid>
		<description>[...] Twitter Downtime On the Upswing Twitter Downtime in 2007 (tags: twitter)    Posted in Links &#124;     Leave a Comment [...]</description>
		<content:encoded><![CDATA[<p>[...] Twitter Downtime On the Upswing Twitter Downtime in 2007 (tags: twitter)    Posted in Links |     Leave a Comment [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Enterprise Alley mobile edition</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2221074</link>
		<dc:creator>Enterprise Alley mobile edition</dc:creator>
		<pubDate>Thu, 24 Apr 2008 15:18:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2221074</guid>
		<description>[...] His presentation suggested Twitter’s problems were behind them, but in fact some of their biggest stumbles hadn’t occurred [...]</description>
		<content:encoded><![CDATA[<p>[...] His presentation suggested Twitter’s problems were behind them, but in fact some of their biggest stumbles hadn’t occurred [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amateur Hour Over At Twitter? &#124; crown.MONKEY</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2220369</link>
		<dc:creator>Amateur Hour Over At Twitter? &#124; crown.MONKEY</dc:creator>
		<pubDate>Thu, 24 Apr 2008 09:53:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2220369</guid>
		<description>[...] His presentation suggested Twitter&#8217;s problems were behind them, but in fact some of their biggest stumbles hadn&#8217;t occurred yet. Note in particular slide 9 of that presentation, where Cook [...]</description>
		<content:encoded><![CDATA[<p>[...] His presentation suggested Twitter&#8217;s problems were behind them, but in fact some of their biggest stumbles hadn&#8217;t occurred yet. Note in particular slide 9 of that presentation, where Cook [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amateur Hour Over At Twitter?</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2217775</link>
		<dc:creator>Amateur Hour Over At Twitter?</dc:creator>
		<pubDate>Wed, 23 Apr 2008 15:30:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2217775</guid>
		<description>[...] His presentation suggested Twitter&#8217;s problems were behind them, but in fact some of their biggest stumbles hadn&#8217;t occurred yet. Note in particular slide 9 of that presentation, where Cook [...]</description>
		<content:encoded><![CDATA[<p>[...] His presentation suggested Twitter&#8217;s problems were behind them, but in fact some of their biggest stumbles hadn&#8217;t occurred yet. Note in particular slide 9 of that presentation, where Cook [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter May Not Have To Care About Uptime Any Longer</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2213643</link>
		<dc:creator>Twitter May Not Have To Care About Uptime Any Longer</dc:creator>
		<pubDate>Tue, 22 Apr 2008 18:44:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2213643</guid>
		<description>[...] used to speculate that Twitter&#8217;s persistent downtime and overall poor service quality could result in a Friendster-type nose dive. But after a three day weekend [...]</description>
		<content:encoded><![CDATA[<p>[...] used to speculate that Twitter&#8217;s persistent downtime and overall poor service quality could result in a Friendster-type nose dive. But after a three day weekend [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Many Challenges of Social Network Sites</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2009572</link>
		<dc:creator>The Many Challenges of Social Network Sites</dc:creator>
		<pubDate>Thu, 28 Feb 2008 13:46:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-2009572</guid>
		<description>[...] Networks have hard time scaling Facebook and Twitter (yes a social network too) are suffering from scaling issues, as a result, their sites have a great deal of downtime or latency. The complicated applications [...]</description>
		<content:encoded><![CDATA[<p>[...] Networks have hard time scaling Facebook and Twitter (yes a social network too) are suffering from scaling issues, as a result, their sites have a great deal of downtime or latency. The complicated applications [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andrew c. &#187; Open Letter to Google</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1988950</link>
		<dc:creator>andrew c. &#187; Open Letter to Google</dc:creator>
		<pubDate>Wed, 13 Feb 2008 23:21:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1988950</guid>
		<description>[...] a little while if I need to; and it is also spam-free so life is good.  Except the whole &#8220;Server is Down&#8221; thing.  and while they have cute little pages to tell you they are broken, it still [...]</description>
		<content:encoded><![CDATA[<p>[...] a little while if I need to; and it is also spam-free so life is good.  Except the whole &#8220;Server is Down&#8221; thing.  and while they have cute little pages to tell you they are broken, it still [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IT&#8217;s About Uptime - The StackSafe Blog &#187; Is 6 Days Too Much Annual Downtime? &#8211; A Question Almost Too Surprising to be Asked</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1921880</link>
		<dc:creator>IT&#8217;s About Uptime - The StackSafe Blog &#187; Is 6 Days Too Much Annual Downtime? &#8211; A Question Almost Too Surprising to be Asked</dc:creator>
		<pubDate>Tue, 15 Jan 2008 21:02:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1921880</guid>
		<description>[...] GigaOM relates that fame has led to the Twitter downtime. Similarly, TechCrunch ascribes the Twitter outages to growing pains. An entire conversation even began among passionate “twitterers” over architectural [...]</description>
		<content:encoded><![CDATA[<p>[...] GigaOM relates that fame has led to the Twitter downtime. Similarly, TechCrunch ascribes the Twitter outages to growing pains. An entire conversation even began among passionate “twitterers” over architectural [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 2007 Had Its Share Of Internet Woes : New Web 2.0 Magazine</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1881082</link>
		<dc:creator>2007 Had Its Share Of Internet Woes : New Web 2.0 Magazine</dc:creator>
		<pubDate>Fri, 28 Dec 2007 09:15:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1881082</guid>
		<description>[...] was the mundane, such as Twitter&#8217;s frustrating downtime. And there were more dramatic moments, like when a truck slammed into a power transformer and [...]</description>
		<content:encoded><![CDATA[<p>[...] was the mundane, such as Twitter&#8217;s frustrating downtime. And there were more dramatic moments, like when a truck slammed into a power transformer and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maximilian Schulz</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1874610</link>
		<dc:creator>Maximilian Schulz</dc:creator>
		<pubDate>Wed, 26 Dec 2007 02:02:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1874610</guid>
		<description>Well… I do not really follow the entire Twitter hype and therefore I have no knowledge about their potential cash flow. But I imagine the cash flows are not that good: who is responsible for the server setup. Hiring a team of professional can be pretty expensive for a startup with bad financing. I do not wanna support Twitter, but I know it from similar experiences, that having a good idea and finding the perfect technical solution are two very different things - especially if you cannot afford external support / knowledge.</description>
		<content:encoded><![CDATA[<p>Well… I do not really follow the entire Twitter hype and therefore I have no knowledge about their potential cash flow. But I imagine the cash flows are not that good: who is responsible for the server setup. Hiring a team of professional can be pretty expensive for a startup with bad financing. I do not wanna support Twitter, but I know it from similar experiences, that having a good idea and finding the perfect technical solution are two very different things - especially if you cannot afford external support / knowledge.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mickaël Rémond</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1861375</link>
		<dc:creator>Mickaël Rémond</dc:creator>
		<pubDate>Fri, 21 Dec 2007 12:46:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1861375</guid>
		<description>Hello Jinc,

If you know a bit what you were talking about you would know that XMPP service is not the problem, being very marginal in Twitter architecture.
And from what I know ejabberd has been rock solid for Twitter, unless you have other information</description>
		<content:encoded><![CDATA[<p>Hello Jinc,</p>
<p>If you know a bit what you were talking about you would know that XMPP service is not the problem, being very marginal in Twitter architecture.<br />
And from what I know ejabberd has been rock solid for Twitter, unless you have other information</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jinc</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1859807</link>
		<dc:creator>Jinc</dc:creator>
		<pubDate>Thu, 20 Dec 2007 23:23:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1859807</guid>
		<description>their XMPP server can not scale and therefore they have an unstable service. As more and more twitters tweet, the more and more outages they will have. they need to reconsider their XMPP server.</description>
		<content:encoded><![CDATA[<p>their XMPP server can not scale and therefore they have an unstable service. As more and more twitters tweet, the more and more outages they will have. they need to reconsider their XMPP server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Warfield</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1859138</link>
		<dc:creator>Bob Warfield</dc:creator>
		<pubDate>Thu, 20 Dec 2007 19:50:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1859138</guid>
		<description>Personally, I wonder if Twitter would have fared better if it had been built on something like Amazon's Web Services.  The potential to scale up and down rapidly is there.  They could even create a duplicate service pretty cheaply to try out new architectures.

More on my blog:

http://smoothspan.wordpress.com/2007/12/18/what-if-twitter-was-built-on-amazons-cloud/</description>
		<content:encoded><![CDATA[<p>Personally, I wonder if Twitter would have fared better if it had been built on something like Amazon&#8217;s Web Services.  The potential to scale up and down rapidly is there.  They could even create a duplicate service pretty cheaply to try out new architectures.</p>
<p>More on my blog:</p>
<p><a href="http://smoothspan.wordpress.com/2007/12/18/what-if-twitter-was-built-on-amazons-cloud/" rel="nofollow">http://smoothspan.wordpress.co.....ons-cloud/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lars Fischer</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1859080</link>
		<dc:creator>Lars Fischer</dc:creator>
		<pubDate>Thu, 20 Dec 2007 19:28:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1859080</guid>
		<description>Highrise by 37signals can scale and it's fast (Rails). So it's either poor design or a bad production setup.</description>
		<content:encoded><![CDATA[<p>Highrise by 37signals can scale and it&#8217;s fast (Rails). So it&#8217;s either poor design or a bad production setup.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Intercon</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1859033</link>
		<dc:creator>Intercon</dc:creator>
		<pubDate>Thu, 20 Dec 2007 19:10:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1859033</guid>
		<description>And remember also that Twitter is not a nobody nomoney company -
Twitter is co-founded by Evan Williams, who was the creator of Blogger, which was previously acquired by Google.</description>
		<content:encoded><![CDATA[<p>And remember also that Twitter is not a nobody nomoney company -<br />
Twitter is co-founded by Evan Williams, who was the creator of Blogger, which was previously acquired by Google.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Intercon</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1859007</link>
		<dc:creator>Intercon</dc:creator>
		<pubDate>Thu, 20 Dec 2007 18:55:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1859007</guid>
		<description>@Jason
thanks for noting the amusement, obviously too cool to be correct -
 if computing is becoming some utility.. imagine electricity
henceforth, no new water, just meta water!</description>
		<content:encoded><![CDATA[<p>@Jason<br />
thanks for noting the amusement, obviously too cool to be correct -<br />
 if computing is becoming some utility.. imagine electricity<br />
henceforth, no new water, just meta water!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Intercon</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1858993</link>
		<dc:creator>Intercon</dc:creator>
		<pubDate>Thu, 20 Dec 2007 18:49:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1858993</guid>
		<description>@Jason
Solution for those who need better solutions.. which do not necessarily entail some problem.. or what're the problems with this guy: http://timoreilly.jaiku.com (whose life I've no envy of..)</description>
		<content:encoded><![CDATA[<p>@Jason<br />
Solution for those who need better solutions.. which do not necessarily entail some problem.. or what&#8217;re the problems with this guy: <a href="http://timoreilly.jaiku.com" rel="nofollow">http://timoreilly.jaiku.com</a> (whose life I&#8217;ve no envy of..)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bta</title>
		<link>http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1858992</link>
		<dc:creator>bta</dc:creator>
		<pubDate>Thu, 20 Dec 2007 18:48:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2007/12/20/twitter-downtime-on-the-upswing/#comment-1858992</guid>
		<description>@Tony:

&#62;It’s actually got a huge volume of messaging going through a lot of channels 
&#62; (web, IM, SMS, API). That makes it a more complicated application than you 
&#62; experience as a user.

Now, now, there are over 20 years of research into how to effectively deal with loads of volume and managing large amounts of data flow.  And most companies do it very well (think of how much data your banking and other financial firms deal with -- some of them even have to have end-to-end processing times [for all activities] in the milliseconds).  

Just because it's a "web 2.0" app, it doesn't get away scot-free on good design and management. 

So, yes, just because it has "a lot of data flow" (and let's be honest a high volume of 140-character messages isn't exactly earth-shattering load) - doesn't mean it isn't simple.  It does two things: take messages in, and send them out (with an absurdly simplistic UI to boot). 

Web-based email services like gmail and yahoo, have much higher volumes of data and do much more complex work with it - yet don't quite have the downtime.</description>
		<content:encoded><![CDATA[<p>@Tony:</p>
<p>&gt;It’s actually got a huge volume of messaging going through a lot of channels<br />
&gt; (web, IM, SMS, API). That makes it a more complicated application than you<br />
&gt; experience as a user.</p>
<p>Now, now, there are over 20 years of research into how to effectively deal with loads of volume and managing large amounts of data flow.  And most companies do it very well (think of how much data your banking and other financial firms deal with &#8212; some of them even have to have end-to-end processing times [for all activities] in the milliseconds).  </p>
<p>Just because it&#8217;s a &#8220;web 2.0&#8243; app, it doesn&#8217;t get away scot-free on good design and management. </p>
<p>So, yes, just because it has &#8220;a lot of data flow&#8221; (and let&#8217;s be honest a high volume of 140-character messages isn&#8217;t exactly earth-shattering load) - doesn&#8217;t mean it isn&#8217;t simple.  It does two things: take messages in, and send them out (with an absurdly simplistic UI to boot). </p>
<p>Web-based email services like gmail and yahoo, have much higher volumes of data and do much more complex work with it - yet don&#8217;t quite have the downtime.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.092 seconds -->
