Many companies are on the verge of deciding to use cloud computing. In this type of decision-making processes, the migration to the cloud is always included and well written. But an equally important issue is the question how free you are when you return or change your provider. What, when your needs changes or you are dissatisfied.
It is always technically possible to change from cloud provider. But what about the costs, time, complexity? Besides technical stuff you want to look at contractual terms as well. I am convinced that they provide good technical solutions. I am also convinced they are good in contractual obligations. So there must be people outside the IT department who are skilled in this too. Cloud initiatives often seem to have lower capital costs but are expensive in the long term. I also assume once in a while you change. It will not last for more than 10 years I guess. Time changing. Perhaps your company is acquired by a company that has a large data center of it's own. Maybe another provider offers better conditions or lower costs. Enough reasons to change once in a while.
The question is how you get your stuff out of the cloud? How does this works? I mean, everyone talks about getting his stuff into the cloud. Not back or from left to right. How are you supported during this job by your provider? Let's be honest. You will be helped by all sides migrating to the cloud but they are often less helpful as you go. Don't get me wrong. I am not agains Cloud computing. It is and will be the future. A couple of years from now a lot of application wil be served by the Cloud. But existing applications are often not ready for the cloud. Often they are also customized or exotic. So standardization is verry important. And when you are an enterprise organization, you are anything but standard. So that's a challenge. My feeling is that there is a bigger market for small companies then for enterprises. But that aside.
Designing and building cloud computing-based systems is nothing like building traditional applications and business systems. If you seriously think about this option, you must be prepared. Be honest, you don't threw your infrastructure from one day to another into the cloud. In my opinion it's just a ridiculous idea to think that simple about it. But I do not think about the people that do.
A well-architected infrastructure is critical to a sustainable cloud strategy.
When you planning a journey to the cloud, you defining a cloud environment for your customers. Not your IT department. It's important you gain knowledge in planning and designing a seamless, automated, highly- optimized cloud-ready virtualized infrastructure leading to defining IT-as-a-Service environment. Develop and validate your capabilities to architect cloud-based solutions and deploy IT-as-a-Service. Improve business agility. It sounds like a cliché but I'm convinced it's true. Invest in Knowledge! When you're ready you'll be less surprised by my first statements. It's better than spending all that time and money on a bad cloud.