<?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: Fault Isolative Architectures or “Swimlaning”</title>
	<atom:link href="http://akfpartners.com/techblog/2008/05/30/fault-isolative-architectures-or-%e2%80%9cswimlaning%e2%80%9d/feed/" rel="self" type="application/rss+xml" />
	<link>http://akfpartners.com/techblog/2008/05/30/fault-isolative-architectures-or-%e2%80%9cswimlaning%e2%80%9d/</link>
	<description>Technical and Leadership Thoughts</description>
	<pubDate>Tue, 06 Jan 2009 10:10:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Abbott, Keeven, Fisher &#38;#038 Fortuna Consulting</title>
		<link>http://akfpartners.com/techblog/2008/05/30/fault-isolative-architectures-or-%e2%80%9cswimlaning%e2%80%9d/comment-page-1/#comment-102</link>
		<dc:creator>Abbott, Keeven, Fisher &#38;#038 Fortuna Consulting</dc:creator>
		<pubDate>Thu, 02 Oct 2008 14:34:06 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2008/05/30/fault-isolative-architectures-or-%e2%80%9cswimlaning%e2%80%9d/#comment-102</guid>
		<description>[...] The next step is to implement systems that answer the question of “which systems are causing the problem”?.  In the ideal world you will have developed a fault isolative architecture to create “failure domains” that will isolate failures and help you determine the systems causing the problem.  Failing that, you need monitoring that can help indicate the rough areas of concern.  These are typically aggregated system statistics and monitoring similar to the real time application monitoring above (susbsystem X is throwing errors at a rate 3 standard deviations above normal) or aggregated load, cpu, etc for a group of systems (rather than a single system).  You want to ensure that this level of monitoring does not create a level of noise that forces your team to ignore the alerts. [...]</description>
		<content:encoded><![CDATA[<p>[...] The next step is to implement systems that answer the question of “which systems are causing the problem”?.  In the ideal world you will have developed a fault isolative architecture to create “failure domains” that will isolate failures and help you determine the systems causing the problem.  Failing that, you need monitoring that can help indicate the rough areas of concern.  These are typically aggregated system statistics and monitoring similar to the real time application monitoring above (susbsystem X is throwing errors at a rate 3 standard deviations above normal) or aggregated load, cpu, etc for a group of systems (rather than a single system).  You want to ensure that this level of monitoring does not create a level of noise that forces your team to ignore the alerts. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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