Top 3 cloud migration mistakes: summer 2019 version

By | August 12, 2019

If you are in the process of migrating workloads into the cloud, then odds are this isn’t your first rodeo. The majority of these doing cloud migrations are in their second or third job. When you’d think we are getting more experienced, we are also seeing a rise in migration failures. Listed below are the top 3 issues I visit and ways to prevent them:

First: no bigger vision past the projects. We are building clouds by utilizing strategic microarchitectures which are normally concentrated around a brief sprint and a couple of workloads. Thuswe enhance our cloud design every moment. Soon we will be in cloud sophistication hell, without the shared services, such as ordinary security, governance, handling, and tracking.

It is simple enough to know how to take care of the issue, but difficult for IT to achieve that. There has to be some frequent macroarchitectural attempts, such as defining services that are common, and also a shared comprehension of the cloud will be into the larger venture. For some reasonwe do not like to consider cloud computing more duration, and that is going to kill the worth you are in a position to escape cloud.

Secondly: lacking devops as part of this transformation. If you are moving to cloud, then probably you have to proceed to devops too. It is a variant of this razor and razor blade version so far as I am concerned, but many businesses are still not making the links.

By now we understand how to install devops, and we all know that it lets you get the maximum from the cloud, for example rate to installation, agility, and analyzing. Alas, a number of ventures seem at devops as a tool which may be bolted on at the close of their migrations. That will not work. Really, I am not certain how you can migrations with no devops.

Third: not performing knowledge transfer. That is just another people issue. Now teams operate on different jobs, gain a lot of expertise on these jobs, but share nothing.

There has to be a central repository to collect artifacts, code samples, and lessons learned. I am discovering that cloud crews do so badly, if at all. The outcome is individuals make the very same mistakes over and over again, and nothing improves.

It is a simple fix but you may have to create some inspiration. For example, on previous endeavors I gave out $50 gift cards for every artifact supplied or recorded lesson learned. Participation increased to the advantage of $1 million (estimated), and cost me $5,000 in gift cards. That is a bargain I will do daily.

Happy summer!