Lift and shift is simple to say, not to do. It’s going to be messy. If you’re considering moving to the cloud, you’re right to be concerned about the vast changes that will be required as you make your transition. The good news is that if you’re like most companies, you’ve done this before. Many times. About every three to five years you overhaul your core architectures. You adjust how you deliver applications. You strive to increase performance, enhance security, and reduce costs. The bad news is that with cloud, things will be even more complicated. You might not have control over services. You may not be able to hard code connections or do things the old way.
Developers are having a greater impact on how applications are architected, and in many cases, making unilateral choices that are in effect making business decisions for the company. While nearly two-thirds of enterprise IT managers believe they should be the deciding vote in selecting a public cloud service, moving apps to the cloud, or creating a private cloud, business units disagree about 40 percent of the time. CIOs need to manage this.
If you want to work at the speed that private cloud can enable, you’ll have to remove as much human latency from your process as possible. As Tesla CEO Elon Musk famously put it, “you can’t have people in the production line itself, otherwise you drop to people speed.”
As an organization, you face a daunting challenge: how can you reap the rewards of private cloud while mitigating the risks? When does private cloud make sense?