Live data from Hacker News

Don't blame Amazon for your lack of redundancy

cloudability.com

1–10 of 23 posts

Re: Don't blame Amazon for your lack of redundancy

#4
Cloud = Virtualization. Creating redundancy within the same virtual ecosystem is idiotic, as the article points out. Any hardware or virtualization software failure would throw your redundancy out the window. You need to have your virtual eggs in very different baskets, in different geographical locations, with different providers.

Re: Don't blame Amazon for your lack of redundancy

#5

The zeitgeist is that the cloud equals redundacy yet that's not necessarily the case. You still need to prep for contingencies...

It is redundant to a degree, but there are varying layers of redundancy.

In this case, it looks like most users of AWS are in need of more geographic redundancy, but in terms of localized data redundancy (term?), it appears AWS is a pretty solid solution.

Re: Don't blame Amazon for your lack of redundancy

#6
post #5

The zeitgeist is that the cloud equals redundacy yet that's not necessarily the case. You still need to prep for contingencies...

It is redundant to a degree, but there are varying layers of redundancy. In this case, it looks like most users of AWS are in need of more geographic redundancy, but in terms of localized data redundancy (term?), it appears AWS is a pretty solid solution.

That's totally right: it's a pretty solid solution and frankly, even with the outage, it's still better than the alternatives based on cost and difficulty of configuration.

Re: Don't blame Amazon for your lack of redundancy

#9
post #7

Your own servers go down too. And not every site can afford triple redundancy. Sometimes you just stay down for a few hours.

+1 Sometimes it's not cost effective to do all the layers. One of our clients is going to lose $2500 to $3000 today, which is less than they would have spent on avoiding the issue in the first place.

Re: Don't blame Amazon for your lack of redundancy

#10
post #4

Cloud = Virtualization. Creating redundancy within the same virtual ecosystem is idiotic, as the article points out. Any hardware or virtualization software failure would throw your redundancy out the window. You need to have your virtual eggs in very different baskets, in different geographical locations, with different providers.

+1 We agree.
Post reply on HN