Refactor or re-architect
Using this strategy, you move an application to the cloud and modify its architecture by taking full advantage of cloud-native features to improve agility, performance, and scalability. This is driven by strong business demand to scale, accelerate product and feature releases, and to reduce costs.
The following are common use cases for the refactor migration strategy:
The legacy mainframe application can no longer address the demand of the business due to its limitations or is expensive to maintain.
You have a monolith application that is already hindering efforts to deliver product quickly or address customer needs and demands.
You have a legacy application that nobody knows how to maintain, or the source code is unavailable.
The application is difficult to test, or test coverage is very low. This affects the quality and delivery of new application features and fixes. By redesigning the application for the cloud, you can increase the test coverage and integrate automated testing tools.
For security and compliance reasons, when moving a database to the cloud, you might need to extract some tables (such as customer information, patient, or patient diagnosis tables) and retain those tables on premises. In this situation, you need to refactor your database in order to separate the tables that will be migrated from those that will be retained on premises.
Watch video The 5th Cloud Migration Strategy | REFACTOR or RE-ARCHITECT online, duration hours minute second in high quality that is uploaded to the channel Cloud Simplified 14 April 2024. Share the link to the video on social media so that your subscribers and friends will also watch this video. This video clip has been viewed 176 times and liked it 5 visitors.