One interesting and oft missed aspect of (at least AWS) Cloud Computing is that the need for DR is somewhat mitigated in that data is replicated behind the scenes by the provider within their infrastructure. What that means IMO is that we are viewing the need for DR in a traditional enterprise model still while moving to the Cloud–notably a completely different approach to computing in general.

Cloud providers have SLAs and therefore have a vested interest in NOT losing your data. In that sense and finally, service providers have stepped up to the plate and have raised the availability bar in their IaaS. While it does not eliminate the need for DR and BC planning, it does not necessarily double the cost of your enterprise when considering a DR strategy.

I think that one of the biggest mistakes and misconceptions is that my enterprise and infrastructure costs will be drastically reduced by just moving my existing architecture into the Cloud.

In simple terms, owning a server means that you can ramp up the processors, memory, storage and network as much as you want and it won’t cost you a dime more than you have invested in it. Take that strategy to the Cloud and you’d better make sure that resource consumption leads to revenue generation or you’ll be supremely disappointed that you made the move.

We just need to think somewhat differently about computing. It’s more like a hotel: rent a resource (room), pay for other services (laundry, room service and even that $8 bottle of water), then check out. If friends come over, add another room to the bill for as long as it is needed. No long term contract. In the old days of the west, families used to live in hotels. The Cloud is not that different, heck, there are already hustlers and rustlers trying to break in an steal things–especially off the new cowboy who just bellied up to the hotel bar.

(Tipping hat)Mighty fine article. Much obliged.