Whew! I’m safe! I’m in the cloud, I don’t need a disaster plan!
Please don’t agree with me. I had chills just writing that. Look, it is very exciting to be out of the datacenter business. No more worries about cabinets, cables, or cooling. No more pesky power issues, counting rack units, or server procurement. 100% software defined datacenter, baby! It’s a dream and the conclusion of a many-year strategy for many. Or perhaps you’re one of the new, hip kids living the dream with containers and continuous integration.
Sure, many clouds can offer uptime SLAs, security, and features that many individual businesses could not duplicate, and we can assume, if you are now all-in-cloud, that your business uptime requirements are met when the cloud meets their SLA. However, the most important questions to ask is: “Is the business uptime requirement met if my provider doesn’t meet their SLA?” And, if they broke the uptime SLA, you’re out of guarantees. Is the business willing to risk uptime based on that SLA?
A product director of a cloud native application once shared with me her perspective, “The biggest concern is not if you are down during a cloud outage, it’s if your competitor is up.” In other words, if there’s a power outage at your restaurant and the whole city is dark, people don’t blame you, but if the party moves next door because they have lights and cold drinks, you’ve lost customers.
Okay, enough F.U.D. I’m not proposing a belt and suspenders, I’m just proposing an honest assessment of how your business can be resilient even in the cloud. There are generally four methods that businesses choose between for their cloud resiliency strategy:
The purpose of this exploration of cloud resiliency strategies was to get people thinking about their business resiliency even for workloads in the cloud. There are likely many variants on the models I described, but these are the approaches we’ve seen most often.
I’ll close with my new cloud-era toast:
“May all your clouds exceed their SLAs and may your application be resilient when they don’t”.
Mode 1 and Mode 2 are no different. The best way to navigate the rough waters of change is to keep your eye on the facts buried under the hype. Code still runs on CPUs, packets still need to be routed, and the laws of physics haven’t changed. What does change is what these activities look like.
Understand how to bridge the gap between executives and IT management with more productive conversations, learn how to build a better disaster recovery plan and further ensure recovery success.
Why am I laughing louder than anyone else in the room? Well, that’s generally just me, but in this case the cartoonist has clearly seen the battle that ensues in an enterprise when they are looking to take advantage of the promises of anything new.