Why Cloud Migrations Fail — Part 1
If you are the ‘skip to the end’ type of person, just read the ‘Number One Reason App Migration Fail’ , at the very bottom of this article. (Hint: It has nothing to do with the public cloud). Note: No part of this questionnaire may be reproduced without attribution AND specific permission from the author.
A staggering number of cloud migrations fail (even Google couldn’t give me an exact figure, but search for ‘cloud migration failure rates’ and you will be astounded).
This is all the more puzzling, considering the advanced nature of the tooling and the infrastructure available in/on the public cloud today. A decade of migrating applications to the cloud resulted in this series of articles — ‘Why cloud migrations fail’.
These questions are a result of real world observations — and questions that a company should attempt to answer before attempting their next cloud migration.
They range from the seemingly innocuous (does the app use external APIs?) to advanced questions around the High Availability and Native Clustering Requirements of the app. For instance, your native DB Clustering engine may not find a home on the public cloud and you may have to replace clustering with Database Replication (which is, abundantly available on the cloud).
