*AWS Cloud Migration:

what are the 6'rs?

Accumulating application portfolio data and rationalizing it into what AWS

Refer to as the 6 R’s:

• Re-host
• Re-platform
• Re-factor/Re-architect
• Re-purchase
• Retire
• Retain

This is a way to identify what is in the environment, what the interdependencies are, the technical complexity to migrate, and how each program will be migrated.

Re-host:

• Shifts apps without making any modifications. Large scale migrations require enterprises to move swiftly in order to assure business objectives. The cosmic majority of these apps are re hosted.
• GE Oil & Gas discovered that re hosting may save upto 30 percent of its cost even if no cloud improvements were implemented. The majority of re hosting may be automated using tools.

Re-platform:

• It construct a few cloud optimizations to observe a noticeable development. There will be no change to the applications basic architecture.
• A multinational media firm moved many on-premises web servers to AWS. It switched from Web Logic to Apache Tomcat, an open source alternative. This media firm helped millions of amount in licensing expenses by switching to AWS

Re-factor:

• This is provoked by a compelling business requirement to add features, size, or performance that would be hard to accomplish in the application’s current environment.
• This is the most luxurious strategy, but it may also be the most efficient if there is a solid product market fit.

Re-purchase:

• Move away from perpetual licenses and toward a software as a service approach.
• For example : Change from a customer relationship management system to Salesforce.com, an HR system to Workday, or a content management system to Drupal.

Retire:

• Applications that are no longer necessary should be removed. As much as 10 persent to 20 percentof a business IT portfolio is no longer needed and can be switched off.
• These savings can help the business case by directing your team’s attention to the applications that people utilize and dropping the number of apps that you must guard.

Retain:

• All application in the execution phase of a migration, on the other hand
• follows the six step process: Discover, Design, Build, Integrate, Validate, and Cutover
• Discover — The application portfolio analyze if backlog are used in the Discovery stage to recognize the present and future architecture. Discover Business Information and Discover Technical Information are the two types of informations.
• Design — The preferred state is established and recorded during the Designing stage. The AWS architecture, application architecture, and supporting operational components and procedures are all part of the preferred state
• Build — The migration design develops during the Designing stage is performed during the Build stage. The migration teams are provided with the essential resources, and reusable template. The migration strategy for the application is used to decide a migration team.
• Integrate — During the Integrate step, the migration team create the application external connection. The migration team collaborate with exterior service providers and application users to establish connections to the application.
• Validate — Each application undergo a series of particular tests at the Validate stage before being released for the Cutover step. Application specific rollback methods are described inside a rollback playbook, which consist of operations communication strategy for user and identifies integration, application, and performance penalty.
• Cutover — Perform a user acceptability test at this point to guarantee a smooth transition. If the migration fail, follow the rollback method mentioned in the cutover plan.

For any query feel free to contact @ rockstargang182@gmail.com

Thank you!