{"id":183,"date":"2021-09-29T12:47:22","date_gmt":"2021-09-29T10:47:22","guid":{"rendered":"https:\/\/staging.greenboxdesigns.com\/cloud-direct-learning-hub\/wp\/?p=183"},"modified":"2024-11-25T21:37:12","modified_gmt":"2024-11-25T21:37:12","slug":"five-rs-of-application-modernisation","status":"publish","type":"post","link":"https:\/\/clouddirect.net\/learning-hub\/five-rs-of-application-modernisation\/","title":{"rendered":"Five R\u2019s of application modernisation"},"content":{"rendered":"

Over the past five years, the way businesses use the cloud for their applications has changed dramatically \u2013 making it safe to say technology has transformed the way applications are made. With customers relying on SaaS solutions and cloud-based start-ups popping up left right and centre,\u00a0it makes now\u00a0a perfect time to migrate your application to the cloud. But where do you start?<\/span>\u00a0<\/span><\/p>

Application Rationalization<\/strong> is the first step in your migration. Microsoft defines it as; the process of evaluating assets to determine the best way to migration or modernise each asset in the cloud. The best way to analyse your applications environment is by using what Gartner articulately coined as the five\u00a0R\u2019s\u00a0of application modernisation \u2013 this will help you choose the best path for your migration.<\/span>\u00a0<\/span><\/p>

So, when you\u2019re looking to\u00a0modernise\u00a0application make sure you use the rationalization approach that fits your long-term strategy, motivations, and current state environment. Ready to explore the five R\u2019s? Let\u2019s jump in.<\/span>\u00a0<\/span><\/p>

 <\/p>\n

Rehost<\/span>\u00a0<\/span><\/h2>\n

Rehosting an application, more commonly known as a \u2018lift and shift\u2019, makes the least change to the architecture of the application. It is the simplest migration there is as it involves you moving your application from one environment to another. Rehosting your application is suitable for a legacy migration or if you have an IT team with limited cloud knowledge.<\/span>\u00a0<\/span><\/p>

It\u2019s best to rehost when you\u2019re looking to move fast or on-prem is costing your business too much.<\/span>\u00a0<\/span><\/p>

 <\/p>\n

Refactor<\/span>\u00a0<\/span><\/h2>\n

Refactoring an application is when you refactor the code to open your ISV up to new business opportunities. This doesn\u2019t mean making any major overhauls to the code, just updating a few bits here and there to optimise your application.<\/span>\u00a0<\/span><\/p>

Once your application has been refactored, your ISV will have greater cloud efficiency, giving you access to better resources, speed, optimised\u00a0costs\u00a0and the ability to better manage your operations. Once your ISV has refactored your application you will be able to leverage Microsoft tools such as Azure SQL Database Managed Instances, Azure Container Services, Azure\u2019 App Services, Azure Functions and Logic Apps.\u00a0It\u2019s best to refactor when creating a custom application or you don\u2019t want to create or maintain infrastructure.<\/span>\u00a0<\/span><\/p>

 <\/p>\n

Rearchitect<\/span>\u00a0<\/span><\/h2>\n

Before you can even start thinking about moving to the cloud, you need to make sure your application is cloud compatible. Rearchitecting an application is when you completely re-write your application to better fit in the cloud. This is usually the case for a legacy or ageing applications that aren\u2019t compatible with the latest cloud providers.<\/span>\u00a0<\/span><\/p>

The four key reasons why you may want to rearchitect your application\u00a0are:<\/span>\u00a0<\/span><\/p>\n