Changes

Application Modernization (view source)

Revision as of 22:35, 15 March 2019

824 bytes added , 22:35, 15 March 2019

m

no edit summary

Line 281: Line 281:

'''Refactor (Re-Architect)'''

−

~~With a refactoring Make~~ elastic.

+

Refactoring is the most costly and time consuming of all strategies. This is an opportunity to take full advantage of cloud-native architectures by introducing elastic scaling of resources.

−

~~Function as a service~~.

+

Adding disaster recover capabilities is other option for refactoring.

−

~~Add DR~~

+

Migrating away from less common OSes such AIX, UNIX, or Solaris may require extensive changes to the application.

−

~~'''Replace'''~~

+

Due to the high cost of refactoring, this strategy should be applied to high business value applications.

−

SaaS

+

'''Replace (Repurchase)'''

+

This is an opportunity to determine if Software-as-a-Service solutions for some of the COTS or custom built application you may have running today. Migrating to SaaS is an opportunity to access the latest version of that service and to lower lifecycle management burden. For example, if you operate a legacy email application, you may want to take the opportunity to replace it with Office 365.

'''Choose Your Migration Target'''

Scott.levac

428

edits