There are many paths which can be taken on a company’s move to the public cloud. Deciding how to migrate to AWS should be a process that focuses on each individual workload, rather than trying to find a single solution to be used across the board.
There’s no one “right way” to migrate, however, once you’ve assessed your workload, there are a number of paths you can take. The path that you choose depends on a number of factors, including time constraints, level of engineering effort, and resource requirements.
The Four Migration Paths
1. Refactoring for Cloud Native Design
Refactoring for cloud native design is the path that requires the most forethought, planning, engineering effort, and overall time to implement, but benefits from being the most stable solution wherever possible.
A solution that pairs automated pipelines and processes with ready-to-use infrastructure templates.
A partially automated process that uses Infrastructure as Code methods, but also relies on manual intervention from system administrators.
The traditional “lift and shift” method of migration that offers a block-for-block match to the on-premises infrastructure.
Ready to learn more about these four paths and find the right path for your workloads? Download our whitepaper today!