15 Jun
With yesterday's partial outage of Amazon Web Services tearing up Twitter, causing a kerfuffle in the media and blogosphere, and wreaking havoc on the up-time of high profile start-ups like Heroku, Pinerest and Dropbox, it's worth remembering that this isn't the first time this has happened.
It was a little more than a year ago, in April 2011, when a widespread AWS outage had a major impact on sites across the internet, and caused an even bigger stir.
In the days that followed, Standing Cloud CEO Dave Jilk weighed in on some of the key take-aways, including the importance of cross-cloud portability (i.e., Amazon is not the only IaaS provider, and your application should be able to run on more than one), and that cloud deployments should be automated and take cloud server reliability characteristics into account.
In the spirit of "everything old is new again," or (as NBC once tried to get us to believe about summer re-runs), "if you haven't seen it, it's new to you," it's worth revisiting Dave's post in its entirety. You can read it here.
Post new comment