On Fri, 3 Mar 2017 09:30:11 -0600, Elardus Engelbrecht <[email protected]> wrote:
>Vernooij, Kees (ITOPT1) - KLM wrote: > ... > >...giving a link to this [honest] post mortem by the AWS: > >https://aws.amazon.com/message/41926/ > >Just a simple lame typo... ;-) > >Groete / Greetings >Elardus Engelbrecht > The link to the Amazon release was in the article mentioned yesterday. I'm not sure "honest" is the exact word I'd use to describe what Amazon writes :-). There's also some irony (for me) that the most obvious things on that web page are "by the way, take up our service" and "hey, you can eve do it for free". Here's an example of how "well crafted" the item is: "Finally, we want to apologize for the impact this event caused for our customers. While we are proud of our long track record of availability with Amazon S3, we know how critical this service is to our customers, their applications and end users, and their businesses. We will do everything we can to learn from this event and use it to improve our availability even further." Why "finally"? Isn't that the first thing they want to do? Why is it an "event", which doesn't sound very bad? After all, event happens, it's just often spelled differently in that phrase. And it is not lessons learned to improve availability. It is to " improve our availability even further". So it was a good thing. So, full disclosure, everything in the open. Whoops. Somehow it is convenient not to mention or address HOW DID THAT EVER HAPPEN IN THE FIRST PLACE. As has been said, don't you test it first? With something of ever-increasing-scale you don't even rely on "well, it worked OK six months ago". "The Amazon Simple Storage Service (S3) team was debugging an issue causing the S3 billing system to progress more slowly than expected." They were "debugging". It was a "billing" problem. Something causing the billing to "progress more slowly than expected" (does that really sound so bad?). Debugging billing on a live system, and they loose vast numbers of business-availability-hours across vast numbers of websites? Debugging? Really? Seriously? And they can get away with that? Yes, it's all in there. Sort of. Standard PR technique to reveal "everything" so that no-one digs into the revelations, because the revalatory work of the journalist is already done by Amazon themselves. Move along, please, nothing to see here. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
