App and Platform Modernization: Rehost, Refactor, Rearchitect, Rebuild, and Replace
Once you’ve decided to start working with Azure, the process of Cloud migration begins. Several complex decisions play a role in this process, so it makes sense to work according to a carefully draw up a migration strategy.
This strategy bases steps on the status of your current IT environment and links them to the business objectives. Having this knowledge enables you to determine which parts of the IT environment will migrate to the Cloud, in which order, and in which way.
To get you started, this article outlines the five most common migration strategies. These are derived from a Gartner paper (2011), which introduces the 5 Rs of Cloud Rationalization.
Rehost
“Rehost,” also known as “Lift & Shift,” is a common approach to migrating applications to the Cloud. You simply move your application to the Cloud with minimal adjustments to the infrastructure as a whole.
This Infrastructure as a Service (IaaS) enables you to immediately reduce operational costs, free up space in your data center, and considerably accelerate any follow-up to your migration process.
“Refactor” is about customizing applications, so that they’re better aligned with the new Cloud environment. This often includes modifying the application itself and part of the code to make more use of Cloud-native functions and the flexibility that they offer. Essentially, you’re switching to a PaaS model.
Refactoring is a more intensive process than Rehosting, but you’ll achieve much bigger benefits for your organization. Your developers will now be able to re-use languages, containers, and the framework in which they’ve invested. Updates can be made faster, and it goes without saying that you’ll have the same advantages as with Rehost.
Rearchitect
Some obsolete applications aren’t compatible with the Cloud due to architectural decisions made while building the app. In this case, it would be wise to consider “Rearchitecting.” This allows you to divide the application into several functional components that can be individually adapted and further developed. The individual components, or “microservices,” can be individually transferred to the Cloud.
This involves major adjustments and will cost considerably more time and money than the previous Rs. However, the upshot is more flexibility, scalability, and more control over your architecture.
Rebuild
A “Rebuild” migration strategy means that you completely redevelop the application on a PaaS infrastructure – unlike with Rearchitect, where you only modify parts of the application.
Rebuild involves removing existing code and redesigning the application in the Cloud, after which you can utilize innovative features on the Cloud provider’s platform. A Cloud-native application is cheap to use and highly scalable. But watch out: A complete rebuild of your application comes with a price tag.
Replace
A “Replace” migration strategy completely replaces an existing application with SaaS. When existing SaaS applications can provide you with all the necessary functionalities, Replace is an excellent option if you’re looking to save costs related to IT development.
Our Microsoft Azure Cloud Essentials workshop will tell you more about the 5 Rs of Cloud Rationalization. You can attend our workshop for free. Feel free to contact us or sign up here.
Tags
App Modernization
Azure Fundamentals
ISV Roadmap
Possibly interesting as well:
Intercept cloud community day
Netwerk, learn and share your knowledge with other guests at Intercept cloud community day!
Each Azure service has its own SLA with associated terms and conditions; limitations and service credit (service credits). But what does this mean exactly?
A new quarter full of new innovations from Azure. Azure has certainly not been standing still! Nor is there any sign that things are getting quieter. Our expert will tell you more about Azure in this one-time special!
A new year full of new innovations from Azure. Azure has certainly not been standing still! Nor is there any sign that things are getting quieter. Join our expert for a look back at 2022 and forward to 2023!
Choosing between Azure SQL, SQL Managed instance or SQL Server
A question we get asked often at Intercept when we transform an application to Azure is what SQL database to use. In this article, we will tell you more about the possible options, what to pay attention to when making this choice and which database we recommend for which situation.
In this workshop the (fictional) software company Cloud Adventures is central. You will follow them on their journey to and on the Azure Cloud. All associated challenges and pain points will be discussed and we will show you in a clear manner how to tackle these problems. Get the most out of the workshop and take the opportunity to ask all your questions to one of our Azure Experts.
The evolution of AKS: from Containers to Kubernetes to Azure Kubernetes Service (AKS)
For some time now [Azure] Kubernetes is thé platform to orchestrate containers. Why is this and what are the benefits of using Kubernetes and managed Kubernetes (AKS)?
Which Azure Cloud Services Are Relevant for My Organization?
Azure has a range of services for every kind of Cloud computing that complement your environment. There are numerous Azure Cloud Services to choose from. This article discusses the most important and relevant services for your organization.
How to reach your audience by utilizing the Microsoft Marketplace
The Microsoft Azure Marketplace. What exactly is it and how can you leverage the power of the Azure Marketplace? Did you know that many companies are already using the marketplace without even being aware? In this article we will dive into the basics of the Azure Marketplace and how you can leverage the benefits.
Software as a service is a model for software licensing that is rapidly becoming the norm in business. But why do so many software companies transfer to SaaS? And what impact does this have on the business process of the ISV?
The Cloud is even with a lot of data traffic the solution for ISVs
Many organizations, mainly ISVs, think that moving to the Public Cloud comes with high costs. This does not have to be the case at all. In fact, moving to the Public Cloud is often more cost beneficial.
Checklist part 2: Choose your architecture before you migrate to Azure
As a second in a series of articles, we’ll take a look at architectures and why it is important to take a look at the overall picture. Do you want to define a roadmap and see where you are in 3 years? Probably not. But you do want to understand the implications your architecture has on added value, available features and pricing.
Checklist part 1: Choose your strategy before you migrate to Azure
Before you start your Azure journey it’s important to take a step back and think of what you’re trying to achieve. The first step to successfully modernizing your solution is to determine your strategy, short term and long term.
Top 5 Azure PaaS and serverless services you don't want to miss as an ISV
We work daily with multiple Independent Software Vendors (ISVs) to optimize their solution using Microsoft Azure. Since we encounter a number of PaaS services on a daily basis with our clients, we want to share our top 5 with you.
The world never stands still, especially in the world of an ISV. So a key question for a software company is: how do I stay up-to-date? Microsoft Azure can help you do just that.
