<?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: when it all goes horribly wrong</title>
	<atom:link href="http://www.darrylking.com.au/2008/04/10/when-it-all-goes-horribly-wrong/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.darrylking.com.au/2008/04/10/when-it-all-goes-horribly-wrong/</link>
	<description>anecdotes, stories and insights on what ireckon!</description>
	<pubDate>Thu, 20 Nov 2008 12:02:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Cogman</title>
		<link>http://www.darrylking.com.au/2008/04/10/when-it-all-goes-horribly-wrong/#comment-201</link>
		<dc:creator>Cogman</dc:creator>
		<pubDate>Wed, 09 Apr 2008 22:38:30 +0000</pubDate>
		<guid isPermaLink="false">http://darryl.ireckonblog.com/2008/04/10/when-it-all-goes-horribly-wrong/#comment-201</guid>
		<description>This is exactly the type of thing Google is trying to solve with its new Google App Engine. Too many companies just don't 'get' how much pressure can be put on web servers when demand increases. 

I'll bet a lot of companies haven't actually fully load tested their applications, which is important because then you can put safeguards in place to say when server load reaches X, show a 'sorry huge demand come back later' message. This is far better than a 509, and is kinda cool as a reader of a website to see the 'sorry huge demand' message because you KNOW the content you are trying to read is popular and is going to be worth reading. I see it happen often on Toms Hardware when a new review for the latest and greatest video card comes out ...EVERYONE jumps on and their servers get hit hard, but it's not a problem because they just show a 'sorry come back later' message, which to me is fine, but Google seems to have found a way to fix even this, which we all take as acceptable / best practice server behaviour. Always innovating. I can't wait for the future of the web :-)</description>
		<content:encoded><![CDATA[<p>This is exactly the type of thing Google is trying to solve with its new Google App Engine. Too many companies just don&#8217;t &#8216;get&#8217; how much pressure can be put on web servers when demand increases. </p>
<p>I&#8217;ll bet a lot of companies haven&#8217;t actually fully load tested their applications, which is important because then you can put safeguards in place to say when server load reaches X, show a &#8217;sorry huge demand come back later&#8217; message. This is far better than a 509, and is kinda cool as a reader of a website to see the &#8217;sorry huge demand&#8217; message because you KNOW the content you are trying to read is popular and is going to be worth reading. I see it happen often on Toms Hardware when a new review for the latest and greatest video card comes out &#8230;EVERYONE jumps on and their servers get hit hard, but it&#8217;s not a problem because they just show a &#8217;sorry come back later&#8217; message, which to me is fine, but Google seems to have found a way to fix even this, which we all take as acceptable / best practice server behaviour. Always innovating. I can&#8217;t wait for the future of the web <img src='http://darryl.ireckonblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
</channel>
</rss>
