Why does everything suck?
Exploring the tech marketplace from 10,000 feet
Monday, July 21, 2008
S3 Failure Raises Questions About Cloud Design
I watched with interest this weekend as Amazon S3 went down yet again, and I thought to myself, “there but for the grace of God go I.”
My company is currently developing a cloud based data service called KloudShare. And though KloudShare is basically unrelated to what S3 does, and probably has more similarity to Google’s Big Table or Amazon Simple DB, they are all still data services, and so it got me thinking about how one might architect systems to avoid such messes. Because while people might forgive Amazon, I don’t think a tiny startup like mine is going to have the same latitude Amazon does.
First, looking at Amazon’s computing service called the Elastic Computing Cloud (EC2) is probably instructive as we have been using Amazon EC2 and have had an instance running for well more than six months (probably approaching a year) without a [From Why does everything suck?: S3 Failure Raises Questions About Cloud Design]
Why does everything suck?: S3 Failure Raises Questions About Cloud Design