http://akfpartners.com/techblog/2008/05/30/fault-isolative-architectures-or-%e2%80%9cswimlaning%e2%80%9d/ Technical and Leadership Thoughts Sat, 13 Mar 2010 12:01:53 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://akfpartners.com/techblog/2008/05/30/fault-isolative-architectures-or-%e2%80%9cswimlaning%e2%80%9d/comment-page-1/#comment-523 Tweets that mention Fault Isolative Architectures or “Swimlaning” | AKF Partners Blog -- Topsy.com Tue, 22 Dec 2009 09:30:59 +0000 http://akf-consulting.com/techblog/2008/05/30/fault-isolative-architectures-or-%e2%80%9cswimlaning%e2%80%9d/#comment-523 [...] This post was mentioned on Twitter by Sergio Bossa, Baronne Mouton. Baronne Mouton said: Fault Isolative Architectures or “Swimlaning” | AKF Partners Blog http://ow.ly/16bU6D [...] [...] This post was mentioned on Twitter by Sergio Bossa, Baronne Mouton. Baronne Mouton said: Fault Isolative Architectures or “Swimlaning” | AKF Partners Blog http://ow.ly/16bU6D [...]

]]> http://akfpartners.com/techblog/2008/05/30/fault-isolative-architectures-or-%e2%80%9cswimlaning%e2%80%9d/comment-page-1/#comment-516 Top 10 Internet Startup Scalability Killers – GigaOM Mon, 21 Dec 2009 02:50:59 +0000 http://akf-consulting.com/techblog/2008/05/30/fault-isolative-architectures-or-%e2%80%9cswimlaning%e2%80%9d/#comment-516 [...] failures in certain components don’t impact other zones of functionality. We refer to these fault isolation zones as “swim [...] [...] failures in certain components don’t impact other zones of functionality. We refer to these fault isolation zones as “swim [...]

]]> http://akfpartners.com/techblog/2008/05/30/fault-isolative-architectures-or-%e2%80%9cswimlaning%e2%80%9d/comment-page-1/#comment-102 Abbott, Keeven, Fisher &#038 Fortuna Consulting Thu, 02 Oct 2008 14:34:06 +0000 http://akf-consulting.com/techblog/2008/05/30/fault-isolative-architectures-or-%e2%80%9cswimlaning%e2%80%9d/#comment-102 [...] 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. [...] [...] 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. [...]

]]>