<?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: Defensively Architecting a SaaS Implementation</title>
	<atom:link href="http://www.saasblogs.com/2008/02/07/defensively-architecting-a-saas-implementation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.saasblogs.com/2008/02/07/defensively-architecting-a-saas-implementation/</link>
	<description>Understanding the Software as a Service Revolution</description>
	<pubDate>Fri, 21 Nov 2008 13:58:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Sinclair Schuller</title>
		<link>http://www.saasblogs.com/2008/02/07/defensively-architecting-a-saas-implementation/#comment-33606</link>
		<dc:creator>Sinclair Schuller</dc:creator>
		<pubDate>Fri, 08 Feb 2008 02:30:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.saasblogs.com/2008/02/07/defensively-architecting-a-saas-implementation/#comment-33606</guid>
		<description>The comment just above this comment is a trackback that is worth reading. It point's out that I've equated SaaS to the extreme end of my analogy, and that's absolutely correct. As the author of the post points out (and correctly so) there is more of a continuum to SaaS architectures. I only meant to simplify the analogy to black and white so that I could get the point across. A fair discussion would be to distill my example from a binary form to a more analog one.</description>
		<content:encoded><![CDATA[<p>The comment just above this comment is a trackback that is worth reading. It point&#8217;s out that I&#8217;ve equated SaaS to the extreme end of my analogy, and that&#8217;s absolutely correct. As the author of the post points out (and correctly so) there is more of a continuum to SaaS architectures. I only meant to simplify the analogy to black and white so that I could get the point across. A fair discussion would be to distill my example from a binary form to a more analog one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the capacity : The Titanic is not a SaaS model</title>
		<link>http://www.saasblogs.com/2008/02/07/defensively-architecting-a-saas-implementation/#comment-33553</link>
		<dc:creator>the capacity : The Titanic is not a SaaS model</dc:creator>
		<pubDate>Thu, 07 Feb 2008 19:21:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.saasblogs.com/2008/02/07/defensively-architecting-a-saas-implementation/#comment-33553</guid>
		<description>[...] He recently sent me an article about architecting defensive SaaS deployments , which is something we&#8217;ve talked a lot about in the past. The article proposes a good analogy but I think makes a mistake in equating SaaS architectures as the &#8220;extreme&#8221; end of that analogy, i.e. large cruise ships. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] He recently sent me an article about architecting defensive SaaS deployments , which is something we&#8217;ve talked a lot about in the past. The article proposes a good analogy but I think makes a mistake in equating SaaS architectures as the &#8220;extreme&#8221; end of that analogy, i.e. large cruise ships. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Ammerman</title>
		<link>http://www.saasblogs.com/2008/02/07/defensively-architecting-a-saas-implementation/#comment-33552</link>
		<dc:creator>Matt Ammerman</dc:creator>
		<pubDate>Thu, 07 Feb 2008 18:57:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.saasblogs.com/2008/02/07/defensively-architecting-a-saas-implementation/#comment-33552</guid>
		<description>Sinclair... your metaphor here is quite striking (bad pun intended).  Just to elaborate on the point a bit:  In the world of hosted software (you made the analogy with the on-premise model) and its various iterations - the ASP model maps/mapped well to the illustration of 400 vessels, each carrying a subset of passengers.  Although you might lose one or two vessels on the way from point A to point B, a larger percentage of your passengers arrive safely at their destination.

Because the SaaS model practically dictates the consolidation of your passenger bearing vessels into a mega-vessel... properly architecting resiliency cannot be understated.</description>
		<content:encoded><![CDATA[<p>Sinclair&#8230; your metaphor here is quite striking (bad pun intended).  Just to elaborate on the point a bit:  In the world of hosted software (you made the analogy with the on-premise model) and its various iterations - the ASP model maps/mapped well to the illustration of 400 vessels, each carrying a subset of passengers.  Although you might lose one or two vessels on the way from point A to point B, a larger percentage of your passengers arrive safely at their destination.</p>
<p>Because the SaaS model practically dictates the consolidation of your passenger bearing vessels into a mega-vessel&#8230; properly architecting resiliency cannot be understated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SaaS Blogs - » Defensively Architecting a SaaS Implementation &#171; FR Test Blog</title>
		<link>http://www.saasblogs.com/2008/02/07/defensively-architecting-a-saas-implementation/#comment-33532</link>
		<dc:creator>SaaS Blogs - » Defensively Architecting a SaaS Implementation &#171; FR Test Blog</dc:creator>
		<pubDate>Thu, 07 Feb 2008 16:21:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.saasblogs.com/2008/02/07/defensively-architecting-a-saas-implementation/#comment-33532</guid>
		<description>[...] SaaS Blogs - » Defensively Architecting a SaaS&#160;Implementation     SaaS Blogs - » Defensively Architecting a SaaS Implementation   Your software now becomes a single, centralized heap that is “carrying” thousands of customers. Focus on compartmentalizing resources and supporting system failure, but try to keep any one compartment from being dedicated to some subset of your customers (i.e. when a compartment on a multi-compartment vessel is breached, some subset of the 4,000 passengers did not sink as a result!). [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] SaaS Blogs - » Defensively Architecting a SaaS&nbsp;Implementation     SaaS Blogs - » Defensively Architecting a SaaS Implementation   Your software now becomes a single, centralized heap that is “carrying” thousands of customers. Focus on compartmentalizing resources and supporting system failure, but try to keep any one compartment from being dedicated to some subset of your customers (i.e. when a compartment on a multi-compartment vessel is breached, some subset of the 4,000 passengers did not sink as a result!). [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
