There’s more than one way to migrate app. Creating a detailed strategy that identifies the best pattern(s) for your workloads is essential to accelerating your journey into the cloud and achieving your desired business objectives. Below are some of the top strategies we see adopted most often by cloud customers–
Rehost – Also known as “lift-and-shift”. In a large-scale migration scenario, where you need to migrate and scale quickly to meet a business case-such as a data center lease termination-we find that most workloads are rehosted. Most rehosting can be automated with tools such as CloudEndure Migration.
Re-platform – Sometimes referred to as “lift-tinker-and-shift” This entails making a few cloud optimizations to achieve tangible benefits but without changing the core architecture of the application.
Refactor – Change the way the application is architected and developed, usually done by employing cloud-native features such as building a data lake. Typically, refactoring (or re-architecting) is driven by a strong business need to add features, scale, or improve performance that would otherwise be difficult to achieve in the application’s existing environment. If your organization is looking to boost agility or improve business continuity by moving to a service-oriented architecture (SOA), this strategy may be worth pursuing-even though it is often the most expensive solution.
Relocate – Move vSphere-based applications to AWS without application changes. VMware Cloud on AWS allows you to quickly relocate hundreds of applications virtualized on vSphere to the AWS Cloud in just days and to maintain consistent operations with your VMware Cloud Foundation based environments. Once in the AWS Cloud, your applications are easier to optimize or re-architect to take advantage of the breadth and depth of AWS services.
Repurchase – Replace your current environment, casually referred to as “drop and shop”. This is a decision to move to a newer version of software or purchase an entirely new solution. You may also be looking for a new software licensing model that allows you more flexibility to match your business needs.
Retain – Do nothing, for now. You may have portions of your IT portfolio that you are not ready to migrate or believe are best kept on-premises. Keep in mind that, as more of your portfolio moves to the cloud, allocation of data center expenses across fewer workloads may eventually drive a need to revisit the retained workloads.
Retire – Decommission or archive unneeded portions of your IT portfolio. During the Assess phase, you may come across applications that are no longer being used. By rationalizing your IT portfolio and identifying assets that are no longer useful and can be turned off, you can strengthen your business case and direct your team’s attention toward maintaining the resources that are more widely used.
Choosing the right partner to support your cloud migration will help ensure you follow a structured approach using proven strategies. The right cloud provider brings access to a deep well of best practice methodologies, tools, solutions, and expertise – resources that can help you realize business benefits faster.
For queries, please write to us at firstname.lastname@example.org Path is an AWS Consulting Partner.