<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Online businesses need for Speed</title>
	<atom:link href="http://brettdargan.com/blog/2005/06/02/online-businesses-need-for-speed/feed/" rel="self" type="application/rss+xml" />
	<link>http://brettdargan.com/blog/2005/06/02/online-businesses-need-for-speed/</link>
	<description>&#955; Thoughts and rants</description>
	<lastBuildDate>Mon, 28 Nov 2011 14:13:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Robert</title>
		<link>http://brettdargan.com/blog/2005/06/02/online-businesses-need-for-speed/comment-page-1/#comment-6</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Tue, 21 Jun 2005 10:00:55 +0000</pubDate>
		<guid isPermaLink="false">http://brettdargan.com/blog/?p=47#comment-6</guid>
		<description>The problem with dealing with spikes is the fact that you need to over-resource for them. It&#039;s usually not cost-effective to have sufficent computing power to handle the load.

What you _really_ need is an efficient way to scale your system dynamically, _plus_ a pool of resources shared with other systems that have different usage patterns. This shared pool can then be drawn on to deal with spikes as needed. Sun, for example, is offering such a service to certain sites, and IBM can do similar stuff (which is why IBM handles the major sporting events, for example). However, this is all highly non-trivial.
</description>
		<content:encoded><![CDATA[<p>The problem with dealing with spikes is the fact that you need to over-resource for them. It&#8217;s usually not cost-effective to have sufficent computing power to handle the load.</p>
<p>What you _really_ need is an efficient way to scale your system dynamically, _plus_ a pool of resources shared with other systems that have different usage patterns. This shared pool can then be drawn on to deal with spikes as needed. Sun, for example, is offering such a service to certain sites, and IBM can do similar stuff (which is why IBM handles the major sporting events, for example). However, this is all highly non-trivial.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

