Static versus dynamic cloud migration

It is nine:00 AM on a Wednesday. You’re in the boardroom providing a status update on the most recent migration task that will eliminate most of the vulnerabilities identified throughout the modern pandemic. This is the third migration task, all considerably less than a hundred workloads and ten data sets. All have taken spot in parallel, and all leverage distinct cloud migration groups.

Business leadership notes that the metrics have been quite distinct between the assignments. Challenge One particular reveals just about 80 percent effectiveness in phrases of code refactoring, tests, deployment, stability implementation, and so on. The many others have been closer to 30 and forty percent. Why the discrepancies? 

Most effectiveness concerns occur from dynamic versus static migration approaches and tools. Most men and women who at this time do cloud migrations gravitate toward the distinct processes, approaches, and migration tool suites that worked for previous assignments. This static approach to cloud migration forces a distinct set of processes and tools onto a wide variety of migration assignments and challenge domains. The misuse of distinct processes and tools as generic alternatives typically leads to failure. 

Core to this situation is our drive to uncover a distinct suite of tools and technologies bundles that the business considers finest-of-breed, and our wish to leverage finest practices. We in IT really like to abide by the group: “I study about these tools and this approach that worked for Joe and Jane and Bob at firms form of like mine, so they’ll work for me, way too.” We make the faulty assumption that we eliminate chance by not creating our possess alternatives, even if the alternatives are situational. 

As an specialist in this area, I would really like to list a typical set of migration tools that will address everyone’s needs—code scanners, configuration management, continual integration and improvement, tests tools, and extra. But the actual solution is that your choices of tools and approaches should be centered on the requirements of the programs and databases you are migrating to community clouds–or any other system, for that subject. 

The task requirements and review processes for migration assignments generally include things like, but are not restricted to:

Copyright © 2020 IDG Communications, Inc.