Comments on: How to deal with cloud failure: Live, learn, fix, repeat

By: mortazavi

mortazavi — Wed, 11 Jul 2012 20:54:31 +0000

By pure logic, any physical failure handling subsystem can itself fail. Therefore, there’s we can never say we have a fully failure-proof system.

By: Greg Arnette

Greg Arnette — Sat, 07 Jul 2012 12:35:40 +0000

My thoughts on Risk Management Assessment in the cloud – “The Cheap Cloud versus The Reliable Cloud” – apps and design make the difference – http://www.gregarnette.com/blog/2012/07/the-cheap-cloud-versus-the-reliable-cloud/

By: Chris

Chris — Sat, 07 Jul 2012 08:07:10 +0000

Mr. Arnold’s comments about OpenStack clearly reveals his lack of understanding of the dynamics. He shouldn’t be talking about topics he has no clue on. It doesn’t matter if his resume includes colossal failures like Sun Microsystems and Yahoo, he has absolutely no clue on how open source projects work. Period.

By: winski

winski — Thu, 05 Jul 2012 18:27:41 +0000

Better yet!! NEVER GO THERE….

By: Ravi Thakur

Ravi Thakur — Thu, 05 Jul 2012 18:20:46 +0000

AWS – which doesn’t claim to be a Tier 4 data center, nor has it proven itself to be 100 percent failure proof – has always advocated that customers design for failure, so it’s important to take that advice to heart. To be prepared for a future Amazon outage, it’s critical to design your platform to have a backup option, so customers’ businesses aren’t affected. We were actually one of the first enterprise companies on private beta for Amazon’s EC2 cloud, and having followed Amazon’s advice, we were prepared and our downtime was just minutes, while everyone else was down for hours.
– Ravi Thakur, VP of Services & Support, Coupa (www.coupa.com)

By: Elaad Teuerstein

Elaad Teuerstein — Thu, 05 Jul 2012 09:09:52 +0000

Here’s Nati Shalom’s take on that Amazon outage: http://tinyurl.com/cqh36m8.
He uses the blow that Heroku took to make a point about surviving failures.

From the blog: “Failures are inevitable, and often happen when and where we least expect them to. Instead of trying to prevent failure from happening we should design our systems to cope with failure. …
…The question that comes out of this experience IMO is not necessarily how to deal with failures (those lessons are as old as the mainframe or even older), but rather — why are we failing to implement the lessons?”

By: gooaaway

gooaaway — Thu, 05 Jul 2012 01:50:34 +0000

“As we gain more experience [building globally distributed systems], we encounter failure domains that we haven’t hit before.” ——- Really? No one ever had a Generator or Telephone line or Circuit or equipment FAILURE !? REALLY?!?!? —— These People are AMATEURS…. Redundency, Redundency, Redundency and if then you think its good enough … DO IT AGAIN !! — Its Just going to happen again…

By: Charles T. Betz

Charles T. Betz — Wed, 04 Jul 2012 15:55:09 +0000

This is one of the most intelligent articles I’ve read on this topic. The cycle of failure is inevitable as we build, stabilize, commoditize, and then conceive of some ambitious next step we hope will give us competitive advantage.

By: Shaleen Shah

Shaleen Shah — Wed, 04 Jul 2012 13:08:03 +0000

I have to agree with your insights here – and doing business on the cloud won’t even happen without electricity.. makes you appreciate those who are working hard to provide us with power, 24×7 a year. I wonder if someone can come up with a sustainable solution to manage this risk. Anyway, have a Happy 4th and thanks for sharing this post.

By: Harish Ganesan

Harish Ganesan — Wed, 04 Jul 2012 09:17:14 +0000

Good article. I have shared my thoughts on dealing with cloud failure in this post : High Availability Patterns to AWS overcome outages . URL : http://harish11g.blogspot.in/2012/06/aws-high-availability-outage.html