It’s 9:00 AM on a Wednesday. You’re within the boardroom giving a standing replace on the most recent migration mission that can take away many of the vulnerabilities discovered through the latest pandemic. This is the third migration mission, all lower than 100 workloads and 10 knowledge units. All have taken place in parallel, and all leverage totally different cloud migration groups.
Company management notes that the metrics had been very totally different between the tasks. Project One reveals almost 80 % effectivity when it comes to code refactoring, testing, deployment, safety implementation, and many others. The others had been nearer to 30 and 40 %. Why the variations?
Most effectivity points come up from dynamic versus static migration approaches and instruments. Most individuals who at present do cloud migrations gravitate towards the precise processes, approaches, and migration device suites that labored for previous tasks. This static method to cloud migration forces a selected set of processes and instruments onto all kinds of migration tasks and drawback domains. The misuse of particular processes and instruments as generic options typically results in failure.
Core to this situation is our drive to discover a particular suite of instruments and know-how bundles that the trade considers best-of-breed, and our need to leverage greatest practices. We in IT like to comply with the group: “I read about these tools and this approach that worked for Joe and Jane and Bob at companies kind of like mine, so they’ll work for me, too.” We make the misguided assumption that we take away danger by not making our personal decisions, even when the alternatives are situational.
As an professional on this discipline, I might like to checklist a regular set of migration instruments that can handle everybody’s wants—code scanners, configuration administration, steady integration and growth, testing instruments, and extra. But the true reply is that your choices of instruments and approaches should be based mostly on the necessities of the purposes and databases you might be migrating to public clouds–or some other platform, for that matter.
The mission standards and overview processes for migration tasks usually embody, however are usually not restricted to:
- “As is” platform evaluation
- Application evaluation
- Data evaluation
- Configuration administration plan
- Security migration instruments
- Governance migration instruments
- Refactoring and redeployment
- CI/CD
- Testing and deployment
- Cloudops/IT operations
- …and extra.
The device classes listed above could have totally different options based mostly on the…
