Success hides problems and truth is, Amazon didn't know what hit 'em. Sure there was a man-made error to start with but who would've thought that a self-healing feature actually made things worse. Right out of a movie script if you ask me.
Plan for failure is good reasonable advice but certainly doesn't cover everything and vague for most to truly appreciate and apply. Important to remember that at this stage, there will be trickles about specifics before the fact. But then, this shouldn't stop you with cloud plans.
Be vigilant instead and continue working to get small wins. Much as we know a lot about the cloud, the things we're unaware of - problems that remain out of sight, actually hold the more valuable answers.
To freeze and stop with cloud computing now is the real disaster.
Here are excellent blog posts covering the outage to get you moving in the right cloud direction from hereon:
Final Thoughts on the Five-Day AWS Outage | eWeek
Amazon EC2 Outage Explained and Lessons Learned | InfoQ
Amazon EC2 Outage Explained and Lessons Learned | InfoQ
Cloud computing around the web : April 25- May 1
0 comments:
Post a Comment