Navigating the decision to migrate your applications to the cloud can seem overwhelming, with concerns about setup, security, and governance. However, with projected annual growth take-up rates of 17.9% between 2022 and 2027. Developing a robust cloud migration strategy is a strategic move that cannot be ignored.
Contributing to business continuity and success, this blog provides an overview of cloud migration strategies related to Amazon Web Services (AWS).
Amazon Web Services (AWS) 7R’s
When migrating your applications and data, a carefully considered approach is required to determine migration readiness. The first step is to assess and organise the applications and data you wish to move. To develop the most appropriate plan and the best outcome. To help you do this, we’ve collated the 7Rs of common cloud migration strategies. Which you should evaluate your data against to decide the most applicable:
- Refactor/re-architect: Move and customise an application, taking full advantage of cloud-native features to improve agility, performance and scalability. This typically involves porting the operating system and database. It tends to be driven by business demands to scale whilst reducing costs.
Example: Migrate your on-premises Oracle database to the Amazon Aurora PostgreSQL-Compatible Edition.
- Replatform (lift and reshape): Move an application to the cloud and introduce some optimisation to take advantage of cloud capabilities.
Example: Migrate your on-premises Oracle database to Amazon Relational Database Service (Amazon RDS) for Oracle in the AWS Cloud.
- Repurchase (drop and shop): Switch to a different product, typically from a traditional license to a SaaS model.
Example: Migrate your customer relationship management (CRM) system to Salesforce.com.
- Rehost (lift and shift): Effectively ‘lifting’ an application to the cloud ‘as-is’. With minimal modification to the architecture, authentication, data flow or business processes. To take advantage of cloud capabilities.
Example: Migrate your on-premises Oracle database to Oracle on an EC2 instance in the AWS Cloud.
- Relocate (hypervisor-level lift and shift): Move your infrastructure to the cloud without purchasing new hardware, rewriting applications or modifying existing operations. Thereby ensuring minimal operational impact.
This scenario is specific to VMware Cloud on AWS. Which supports virtual machine (VM) compatibility and workload portability between on-premises environments and AWS. You can use the VMware Cloud Foundation technologies from your on-premises data centres when you migrate your infrastructure to VMware Cloud on AWS.
Example: Relocate the hypervisor hosting your Oracle database to VMware Cloud on AWS.
- Retain (revisit): Retain applications that cannot be retired due to reliance on another application or security and compliance purposes. These might include applications that require major refactoring that you want to delay. And legacy applications that you wish to retain due to no business case for migration.
- Retire: Terminate or downsize applications that are inefficient and no longer required.
We can help
If you are unsure where to start or have concerns due to in-house technical and knowledge constraints. Our expert team at Brightsolid is happy to help you.
Click here to start the conversation.