Post by account_disabled on Dec 6, 2023 4:54:54 GMT -5
This migration strategy involves making changes to the application to adapt it to function in a cloud environment but the functionality itself remains unchanged. When to decide on refactoring? This strategy is recommended when we do not want to lose the functionality of the application data. It will work well for businesscritical systems and applications when we want to maintain business continuity and at the same time improve the quality of the infrastructure. Advantages It allows you to improve your infrastructure. It does not require a complete rebuild of the application. Greater opportunities in the long term for the use of payperuse services. Long term scale and payback. Leverage cloudnative capabilities with refactoring.
The service providers liability is higher than in the case of rehosting. Defects Unlike rehosting little intervention in the application architecture is needed. Inability to introduce major changes in the architecture and thus take advantage of for example the opportunities offered by microservices Higher initial costs than Lift and Shift and greater involvement of technical teams due to changes in Email Marketing List the application. Applications and data management and their protection are the responsibility of the company. Revise i.e. improve According to Gartner improving existing code using the potential of the strategies described above Refactor or Rehost is also an important strategy in cloud migration. This allows the application to be better adapted to function in the providers environment.
When to use revise? It is worth choosing this option when we want to modify the application to a greater extent. Some applications may require a complete architecture change. Advantages Better adaptation to functioning in a cloud environment. Possibility to add new functionalities. Great application customization possibilities. Defects A timeconsuming solution due to significant changes in the code. Difficult to apply to monolithic applications e.g. written in older languages such as Java.
The service providers liability is higher than in the case of rehosting. Defects Unlike rehosting little intervention in the application architecture is needed. Inability to introduce major changes in the architecture and thus take advantage of for example the opportunities offered by microservices Higher initial costs than Lift and Shift and greater involvement of technical teams due to changes in Email Marketing List the application. Applications and data management and their protection are the responsibility of the company. Revise i.e. improve According to Gartner improving existing code using the potential of the strategies described above Refactor or Rehost is also an important strategy in cloud migration. This allows the application to be better adapted to function in the providers environment.
When to use revise? It is worth choosing this option when we want to modify the application to a greater extent. Some applications may require a complete architecture change. Advantages Better adaptation to functioning in a cloud environment. Possibility to add new functionalities. Great application customization possibilities. Defects A timeconsuming solution due to significant changes in the code. Difficult to apply to monolithic applications e.g. written in older languages such as Java.